Device, method, and graphical user interface for simulating and interacting with handwritten text

ABSTRACT

A device receives a user input that corresponds with a sequence of characters. In response to the user input, the device displays simulated handwritten text that includes varying the appearance of characters in the simulated handwritten text based on variations in handwritten text of a respective user. In response to receiving the user input and in accordance with a determination that a first criterion is met, a first character in the sequence of characters has a first appearance that corresponds to the appearance of the first character in handwritten text of the respective user. In accordance with a determination that a second criterion is met, the first character in the sequence of characters has a second appearance that corresponds to the appearance of the first character in handwritten text of the respective user. The second appearance of the first character is different than the first appearance of the first character.

RELATED APPLICATION

This application claims priority to U.S. patent application Ser. No.15/978,127 (filed on May 12, 2018), which itself claims priority to U.S.Provisional Patent Application Nos. 62/514,616 (filed on Jun. 2, 2017)and 62/514,894 (filed on Jun. 4, 2017), and the entire contents of whichare incorporated herein by reference.

TECHNICAL FIELD

The present disclosure relates generally to electronic devices withtouch-sensitive surfaces, including but not limited to electronicdevices with touch-sensitive surfaces that simulate and interact withhandwritten text.

BACKGROUND

The use of touch-sensitive surfaces as input devices for computers andother electronic computing devices has increased significantly in recentyears. Example touch-sensitive surfaces include touchpads andtouch-screen displays. Such surfaces are widely used to manipulate userinterface objects on a display.

Example manipulations include adjusting the position and/or size of oneor more user interface objects or activating buttons or openingfiles/applications represented by user interface objects, as well asassociating metadata with one or more user interface objects orotherwise manipulating user interfaces. Example user interface objectsinclude digital images, video, text, icons, control elements such asbuttons and other graphics. A user will, in some circumstances, need toperform such manipulations on user interface objects in a filemanagement program (e.g., Finder from Apple Inc. of Cupertino, Calif.),an image management application (e.g., Aperture, iPhoto, Photos fromApple Inc. of Cupertino, Calif.), a digital content (e.g., videos andmusic) management application (e.g., iTunes from Apple Inc. ofCupertino, Calif.), a drawing application, a presentation application(e.g., Keynote from Apple Inc. of Cupertino, Calif.), a word processingapplication (e.g., Pages from Apple Inc. of Cupertino, Calif.), awebsite creation application (e.g., iWeb from Apple Inc. of Cupertino,Calif.), a disk authoring application (e.g., iDVD from Apple Inc. ofCupertino, Calif.), or a spreadsheet application (e.g., Numbers fromApple Inc. of Cupertino, Calif.).

But methods for performing these manipulations are cumbersome andinefficient. For example, using a sequence of mouse based inputs toselect one or more user interface objects and perform one or moreactions on the selected user interface objects is tedious and creates asignificant cognitive burden on a user. In addition, these methods takelonger than necessary, thereby wasting energy. This latter considerationis particularly important in battery-operated devices.

SUMMARY

Accordingly, there is a need for electronic devices with faster, moreefficient methods and interfaces for simulating and interacting withhandwritten text. Such methods and interfaces optionally complement orreplace conventional methods for simulating and interacting withhandwritten text. Such methods and interfaces reduce the cognitiveburden on a user and produce a more efficient human-machine interface.For battery-operated devices, such methods and interfaces conserve powerand increase the time between battery charges.

The above deficiencies and other problems associated with userinterfaces for electronic devices with touch-sensitive surfaces arereduced or eliminated by the disclosed devices. In some embodiments, thedevice is a desktop computer. In some embodiments, the device isportable (e.g., a notebook computer, tablet computer, or handhelddevice). In some embodiments, the device has a touchpad. In someembodiments, the device has a touch-sensitive display (also known as a“touch screen” or “touch-screen display”). In some embodiments, thedevice has a graphical user interface (GUI), one or more processors,memory and one or more modules, programs or sets of instructions storedin the memory for performing multiple functions. In some embodiments,the user interacts with the GUI primarily through stylus and/or fingercontacts and gestures on the touch-sensitive surface. In someembodiments, the functions optionally include image editing, drawing,presenting, word processing, website creating, disk authoring,spreadsheet making, game playing, telephoning, video conferencing,e-mailing, instant messaging, workout support, digital photographing,digital videoing, web browsing, digital music playing, and/or digitalvideo playing. Executable instructions for performing these functionsare, optionally, included in a non-transitory computer readable storagemedium or other computer program product configured for execution by oneor more processors.

In accordance with some embodiments, a method is performed at a devicewith a touch-sensitive display, a non-transitory memory and one or moreprocessors coupled with the touch-sensitive display and thenon-transitory memory. The method includes displaying, on thetouch-sensitive display, a drawing region. While displaying, the drawingregion, the method includes detecting a sequence of drawing inputs onthe touch-sensitive display. In response to detecting the sequence ofdrawing inputs, the method includes drawing a plurality of strokes inthe drawing region. The plurality of strokes correspond to a pluralityof characters. After detecting the sequence of drawing inputs on thetouch-sensitive display, the method includes detecting a predefinedgesture that corresponds to a request to perform an operation based onthe plurality of characters represented by the plurality of strokes. Inresponse to detecting the predefined gesture, the method includesconcurrently displaying a first visual prompt indicating that a firstsubset of one or more characters in the plurality of characters can beused to perform the operation and a second visual prompt indicating thata second subset of one or more characters in the plurality of characterscan be used to perform the operation.

In accordance with some embodiments, an electronic device includes atouch-sensitive display unit configured to display a user interface, oneor more input units configured to receive user inputs, and a processingunit coupled with the touch-sensitive display unit, and the one or moreinput units. The processing unit is configured to enable display of, ina display area on the touch-sensitive display unit, a drawing region.The processing unit is configured to while displaying the drawingregion, detecting a sequence of drawing inputs on the touch-sensitivedisplay. In response to detecting the sequence of drawing inputs, theprocessing unit is further configured to draw a plurality of strokes inthe drawing region. The plurality of strokes correspond to a pluralityof characters. After detecting the sequence of drawing inputs on thetouch-sensitive display, the processing unit is configured to detect apredefined gesture that corresponds to a request to perform an operationbased on the plurality of characters represented by the plurality ofstrokes. In response to detecting the predefined gesture, the processingunit is further configured to concurrently display a first visual promptindicating that a first subset of one or more characters in theplurality of characters can be used to perform the operation and asecond visual prompt indicating that a second subset of one or morecharacters in the plurality of characters can be used to perform theoperation.

In accordance with some embodiments, a method is performed at a devicewith a display, a non-transitory memory, one or more processors coupledwith the display and the non-transitory memory, and one or more inputdevices. The method includes receiving, via the one or more inputdevices, a user input that corresponds with a sequence of characters. Inresponse to receiving the user input, the method includes displaying, onthe display simulated handwritten text that includes varying theappearance of characters in the simulated handwritten text based onvariations that were detected in handwritten text of a respective user.In response to receiving the user input and in accordance with adetermination that a first criterion is met, a first character in thesequence of characters has a first appearance that corresponds to theappearance of the first character in handwritten text of the respectiveuser. In response to receiving the user input and in accordance with adetermination that a second criterion is met, the first character in thesequence of characters has a second appearance that corresponds to theappearance of the first character in handwritten text of the respectiveuser. The second appearance of the first character is different than thefirst appearance of the first character.

In accordance with some embodiments, an electronic device includes adisplay unit configured to display a user interface, one or more inputunits configured to receive user inputs, and a processing unit coupledwith the display unit and the one or more input units. The processingunit is configured to receive, via the one or more input units, the userinput that corresponds with a sequence of characters. In response toreceiving the user input, the processing unit is configured to display,on the display unit simulated handwritten text that includes varying theappearance of characters in the simulated handwritten text based onvariations that were detected in handwritten text of a respective user.In response to receiving the user input and in accordance with adetermination that a first criterion is met, a first character in thesequence of characters has a first appearance that corresponds to theappearance of the first character in handwritten text of the respectiveuser. In response to receiving the user input and in accordance with adetermination that a second criterion is met, the first character in thesequence of characters has a second appearance that corresponds to theappearance of the first character in handwritten text of the respectiveuser. The second appearance of the first character is different than thefirst appearance of the first character.

Thus, electronic devices with displays and input devices are providedwith faster, more efficient methods and interfaces for displayingaffordances in accessibility mode. Such electronic devices improve thevisibility of the affordances thereby improving the operability of theelectronic devices. Such methods and interfaces may complement orreplace conventional methods for displaying affordances in accessibilitymode.

BRIEF DESCRIPTION OF THE DRAWINGS

For a better understanding of the various described embodiments,reference should be made to the Description of Embodiments below, inconjunction with the following drawings in which like reference numeralsrefer to corresponding parts throughout the figures.

FIG. 1A is a block diagram illustrating a portable multifunction devicewith a touch-sensitive display in accordance with some embodiments.

FIG. 1B is a block diagram illustrating example components for eventhandling in accordance with some embodiments.

FIG. 2 illustrates a portable multifunction device having a touch screenin accordance with some embodiments.

FIG. 3 is a block diagram of an example multifunction device with adisplay and a touch-sensitive surface in accordance with someembodiments.

FIG. 4A illustrates an example user interface for a menu of applicationson a portable multifunction device in accordance with some embodiments.

FIG. 4B illustrates an example user interface for a multifunction devicewith a touch-sensitive surface that is separate from the display inaccordance with some embodiments.

FIGS. 5A-5Z illustrate example user interfaces for interacting withhandwritten text in accordance with some embodiments.

FIGS. 6A-6Y illustrate example user interfaces for simulatinghandwritten text in accordance with some embodiments.

FIGS. 7A-7D are flow diagrams illustrating a method of interacting withhandwritten text in accordance with some embodiments.

FIGS. 8A-8E are flow diagrams illustrating a method of simulatinghandwritten text in accordance with some embodiments.

DESCRIPTION OF EMBODIMENTS

Typically, a user can adjust a text display setting to adjust a textsize of text that is displayed on the device. However, the text size oftext that is part of an affordance is typically limited by a size of theaffordance. As such, typical adjustments to the text display setting donot improve the visibility of text that is part of an affordance to thesame extent as text that is not part of the affordance. Accordingly, insome embodiments described below, the device displays an overlay thatincludes an enlarged representation of an affordance. Displaying theoverlay allows the device to display an enlarged representation of thetext that is part of the affordance. Since the enlarged representationof the text is not limited by the size of the affordance, displaying theoverlay improves the visibility of the affordance. Improving thevisibility of the affordance makes it easier for the user to see theaffordance thereby improving the user experience.

Below, a description of example devices illustrated in FIGS. 1A-1B, 2,and 3 is provided. FIGS. 4A-4B, and 5A-5Z illustrate example userinterfaces for interacting with handwritten text. FIGS. 7A-7D illustratea flow diagram of a method of interacting with handwritten text. Theuser interfaces in 5A-5Z are used to illustrate the processes in FIGS.7A-7D. FIGS. 6A-6Y illustrate example user interfaces for simulatinghandwritten text. FIGS. 8A-8E illustrate a flow diagram of a method ofsimulating handwritten text. The user interfaces in 6A-6Y are used toillustrate the processes in FIGS. 8A-8E.

Example Devices

Reference will now be made in detail to embodiments, examples of whichare illustrated in the accompanying drawings. In the following detaileddescription, numerous specific details are set forth in order to providea thorough understanding of the various described embodiments. However,it will be apparent to one of ordinary skill in the art that the variousdescribed embodiments may be practiced without these specific details.In other instances, well-known methods, procedures, components,circuits, and networks have not been described in detail so as not tounnecessarily obscure aspects of the embodiments.

It will also be understood that, although the terms first, second, etc.are, in some instances, used herein to describe various elements, theseelements should not be limited by these terms. These terms are only usedto distinguish one element from another. For example, a first contactcould be termed a second contact, and, similarly, a second contact couldbe termed a first contact, without departing from the scope of thevarious described embodiments. The first contact and the second contactare both contacts, but they are not the same contact, unless the contextclearly indicates otherwise.

The terminology used in the description of the various describedembodiments herein is for the purpose of describing particularembodiments only and is not intended to be limiting. As used in thedescription of the various described embodiments and the appendedclaims, the singular forms “a,” “an,” and “the” are intended to includethe plural forms as well, unless the context clearly indicatesotherwise. It will also be understood that the term “and/or” as usedherein refers to and encompasses any and all possible combinations ofone or more of the associated listed items. It will be furtherunderstood that the terms “includes,” “including,” “comprises,” and/or“comprising,” when used in this specification, specify the presence ofstated features, integers, steps, operations, elements, and/orcomponents, but do not preclude the presence or addition of one or moreother features, integers, steps, operations, elements, components,and/or groups thereof.

As used herein, the term “if” is, optionally, construed to mean “when”or “upon” or “in response to determining” or “in response to detecting,”depending on the context. Similarly, the phrase “if it is determined” or“if [a stated condition or event] is detected” is, optionally, construedto mean “upon determining” or “in response to determining” or “upondetecting [the stated condition or event]” or “in response to detecting[the stated condition or event],” depending on the context.

Embodiments of electronic devices, user interfaces for such devices, andassociated processes for using such devices are described. In someembodiments, the device is a portable communications device, such as amobile telephone, that also contains other functions, such as PDA and/ormusic player functions. Example embodiments of portable multifunctiondevices include, without limitation, the iPhone®, iPod Touch®, and iPad®devices from Apple Inc. of Cupertino, Calif. Other portable electronicdevices, such as laptops or tablet computers with touch-sensitivesurfaces (e.g., touch-screen displays and/or touchpads), are,optionally, used. It should also be understood that, in someembodiments, the device is not a portable communications device, but isa desktop computer with a touch-sensitive surface (e.g., a touch-screendisplay and/or a touchpad).

In the discussion that follows, an electronic device that includes adisplay and a touch-sensitive surface is described. It should beunderstood, however, that the electronic device optionally includes oneor more other physical user-interface devices, such as a physicalkeyboard, a mouse and/or a joystick.

The device typically supports a variety of applications, such as one ormore of the following: a drawing application, a presentationapplication, a word processing application, a website creationapplication, a disk authoring application, a spreadsheet application, agaming application, a telephone application, a video conferencingapplication, an e-mail application, an instant messaging application, aworkout support application, a photo management application, a digitalcamera application, a digital video camera application, a web browsingapplication, a digital music player application, and/or a digital videoplayer application.

The various applications that are executed on the device optionally useat least one common physical user-interface device, such as thetouch-sensitive surface. One or more functions of the touch-sensitivesurface as well as corresponding information displayed on the deviceare, optionally, adjusted and/or varied from one application to the nextand/or within a respective application. In this way, a common physicalarchitecture (such as the touch-sensitive surface) of the deviceoptionally supports the variety of applications with user interfacesthat are intuitive and transparent to the user.

Attention is now directed toward embodiments of portable devices withtouch-sensitive displays. FIG. 1A is a block diagram illustratingportable multifunction device 100 with touch-sensitive display system112 in accordance with some embodiments. Touch-sensitive display system112 is sometimes called a “touch screen” for convenience, and issometimes simply called a touch-sensitive display. Device 100 includesmemory 102 (which optionally includes one or more computer readablestorage mediums), memory controller 120, one or more processing units(CPUs) 122, peripherals interface 118, RF circuitry 108, audio circuitry110, speaker 111, microphone 113, input/output (I/O) subsystem 106,other input or control devices 116, and external port 124. Device 100optionally includes one or more optical sensors 164. Device 100optionally includes one or more contact intensity sensors 165 fordetecting intensity of contacts on device 100 (e.g., a touch-sensitivesurface such as touch-sensitive display system 112 of device 100).Device 100 optionally includes one or more tactile output generators 163for generating tactile outputs on device 100 (e.g., generating tactileoutputs on a touch-sensitive surface such as touch-sensitive displaysystem 112 of device 100 or touchpad 355 of device 300). Thesecomponents optionally communicate over one or more communication busesor signal lines 103.

As used in the specification and claims, the term “tactile output”refers to physical displacement of a device relative to a previousposition of the device, physical displacement of a component (e.g., atouch-sensitive surface) of a device relative to another component(e.g., housing) of the device, or displacement of the component relativeto a center of mass of the device that will be detected by a user withthe user's sense of touch. For example, in situations where the deviceor the component of the device is in contact with a surface of a userthat is sensitive to touch (e.g., a finger, palm, or other part of auser's hand), the tactile output generated by the physical displacementwill be interpreted by the user as a tactile sensation corresponding toa perceived change in physical characteristics of the device or thecomponent of the device. For example, movement of a touch-sensitivesurface (e.g., a touch-sensitive display or trackpad) is, optionally,interpreted by the user as a “down click” or “up click” of a physicalactuator button. In some cases, a user will feel a tactile sensationsuch as a “down click” or an “up click” even when there is no movementof a physical actuator button associated with the touch-sensitivesurface that is physically pressed (e.g., displaced) by the user'smovements. As another example, movement of the touch-sensitive surfaceis, optionally, interpreted or sensed by the user as “roughness” of thetouch-sensitive surface, even when there is no change in smoothness ofthe touch-sensitive surface. While such interpretations of touch by auser will be subject to the individualized sensory perceptions of theuser, there are many sensory perceptions of touch that are common to alarge majority of users. Thus, when a tactile output is described ascorresponding to a particular sensory perception of a user (e.g., an “upclick,” a “down click,” “roughness”), unless otherwise stated, thegenerated tactile output corresponds to physical displacement of thedevice or a component thereof that will generate the described sensoryperception for a typical (or average) user.

It should be appreciated that device 100 is only one example of aportable multifunction device, and that device 100 optionally has moreor fewer components than shown, optionally combines two or morecomponents, or optionally has a different configuration or arrangementof the components. The various components shown in FIG. 1A areimplemented in hardware, software, firmware, or a combination thereof,including one or more signal processing and/or application specificintegrated circuits.

Memory 102 optionally includes high-speed random access memory andoptionally also includes non-volatile memory, such as one or moremagnetic disk storage devices, flash memory devices, or othernon-volatile solid-state memory devices. Access to memory 102 by othercomponents of device 100, such as CPU(s) 122 and the peripheralsinterface 118, is, optionally, controlled by memory controller 120.

Peripherals interface 118 can be used to couple input and outputperipherals of the device to CPU(s) 122 and memory 102. The one or moreprocessors 122 run or execute various software programs and/or sets ofinstructions stored in memory 102 to perform various functions fordevice 100 and to process data.

In some embodiments, peripherals interface 118, CPU(s) 122, and memorycontroller 120 are, optionally, implemented on a single chip, such aschip 104. In some other embodiments, they are, optionally, implementedon separate chips.

RF (radio frequency) circuitry 108 receives and sends RF signals, alsocalled electromagnetic signals. RF circuitry 108 converts electricalsignals to/from electromagnetic signals and communicates withcommunications networks and other communications devices via theelectromagnetic signals. RF circuitry 108 optionally includes well-knowncircuitry for performing these functions, including but not limited toan antenna system, an RF transceiver, one or more amplifiers, a tuner,one or more oscillators, a digital signal processor, a CODEC chipset, asubscriber identity module (SIM) card, memory, and so forth. RFcircuitry 108 optionally communicates with networks, such as theInternet, also referred to as the World Wide Web (WWW), an intranetand/or a wireless network, such as a cellular telephone network, awireless local area network (LAN) and/or a metropolitan area network(MAN), and other devices by wireless communication. The wirelesscommunication optionally uses any of a plurality of communicationsstandards, protocols and technologies, including but not limited toGlobal System for Mobile Communications (GSM), Enhanced Data GSMEnvironment (EDGE), high-speed downlink packet access (HSDPA),high-speed uplink packet access (HSDPA), Evolution, Data-Only (EV-DO),HSPA, HSPA+, Dual-Cell HSPA (DC-HSPDA), long term evolution (LTE), nearfield communication (NFC), wideband code division multiple access(W-CDMA), code division multiple access (CDMA), time division multipleaccess (TDMA), Bluetooth, Wireless Fidelity (Wi-Fi) (e.g., IEEE 802.11a,IEEE 802.11ac, IEEE 802.11ax, IEEE 802.11b, IEEE 802.11g and/or IEEE802.11n), voice over Internet Protocol (VoIP), Wi-MAX, a protocol fore-mail (e.g., Internet message access protocol (IMAP) and/or post officeprotocol (POP)), instant messaging (e.g., extensible messaging andpresence protocol (XMPP), Session Initiation Protocol for InstantMessaging and Presence Leveraging Extensions (SIMPLE), Instant Messagingand Presence Service (IMPS)), and/or Short Message Service (SMS), or anyother suitable communication protocol, including communication protocolsnot yet developed as of the filing date of this document.

Audio circuitry 110, speaker 111, and microphone 113 provide an audiointerface between a user and device 100. Audio circuitry 110 receivesaudio data from peripherals interface 118, converts the audio data to anelectrical signal, and transmits the electrical signal to speaker 111.Speaker 111 converts the electrical signal to human-audible sound waves.Audio circuitry 110 also receives electrical signals converted bymicrophone 113 from sound waves. Audio circuitry 110 converts theelectrical signal to audio data and transmits the audio data toperipherals interface 118 for processing. Audio data is, optionally,retrieved from and/or transmitted to memory 102 and/or RF circuitry 108by peripherals interface 118. In some embodiments, audio circuitry 110also includes a headset jack (e.g., 212, FIG. 2). The headset jackprovides an interface between audio circuitry 110 and removable audioinput/output peripherals, such as output-only headphones or a headsetwith both output (e.g., a headphone for one or both ears) and input(e.g., a microphone).

I/O subsystem 106 couples input/output peripherals on device 100, suchas touch-sensitive display system 112 and other input or control devices116, with peripherals interface 118. I/O subsystem 106 optionallyincludes display controller 156, optical sensor controller 158,intensity sensor controller 159, haptic feedback controller 161, and oneor more input controllers 160 for other input or control devices. Theone or more input controllers 160 receive/send electrical signalsfrom/to other input or control devices 116. The other input or controldevices 116 optionally include physical buttons (e.g., push buttons,rocker buttons, etc.), dials, slider switches, joysticks, click wheels,and so forth. In some alternate embodiments, input controller(s) 160are, optionally, coupled with any (or none) of the following: akeyboard, infrared port, USB port, stylus, and/or a pointer device suchas a mouse. The one or more buttons (e.g., 208, FIG. 2) optionallyinclude an up/down button for volume control of speaker 111 and/ormicrophone 113. The one or more buttons optionally include a push button(e.g., 206, FIG. 2).

Touch-sensitive display system 112 provides an input interface and anoutput interface between the device and a user. Display controller 156receives and/or sends electrical signals from/to touch-sensitive displaysystem 112. Touch-sensitive display system 112 displays visual output tothe user. The visual output optionally includes graphics, text, icons,video, and any combination thereof (collectively termed “graphics”). Insome embodiments, some or all of the visual output corresponds touser-interface objects.

Touch-sensitive display system 112 has a touch-sensitive surface, sensoror set of sensors that accepts input from the user based onhaptic/tactile contact. Touch-sensitive display system 112 and displaycontroller 156 (along with any associated modules and/or sets ofinstructions in memory 102) detect contact (and any movement or breakingof the contact) on touch-sensitive display system 112 and converts thedetected contact into interaction with user-interface objects (e.g., oneor more soft keys, icons, web pages or images) that are displayed ontouch-sensitive display system 112. In an example embodiment, a point ofcontact between touch-sensitive display system 112 and the usercorresponds to a finger of the user or a stylus.

Touch-sensitive display system 112 optionally uses LCD (liquid crystaldisplay) technology, LPD (light emitting polymer display) technology, orLED (light emitting diode) technology, although other displaytechnologies are used in other embodiments. Touch-sensitive displaysystem 112 and display controller 156 optionally detect contact and anymovement or breaking thereof using any of a plurality of touch sensingtechnologies now known or later developed, including but not limited tocapacitive, resistive, infrared, and surface acoustic wave technologies,as well as other proximity sensor arrays or other elements fordetermining one or more points of contact with touch-sensitive displaysystem 112. In an example embodiment, projected mutual capacitancesensing technology is used, such as that found in the iPhone®, iPodTouch®, and iPad® from Apple Inc. of Cupertino, Calif.

Touch-sensitive display system 112 optionally has a video resolution inexcess of 100 dpi. In some embodiments, the touch screen videoresolution is in excess of 400 dpi (e.g., 500 dpi, 800 dpi, or greater).The user optionally makes contact with touch-sensitive display system112 using any suitable object or appendage, such as a stylus, a finger,and so forth. In some embodiments, the user interface is designed towork with finger-based contacts and gestures, which can be less precisethan stylus-based input due to the larger area of contact of a finger onthe touch screen. In some embodiments, the device translates the roughfinger-based input into a precise pointer/cursor position or command forperforming the actions desired by the user.

In some embodiments, in addition to the touch screen, device 100optionally includes a touchpad (not shown) for activating ordeactivating particular functions. In some embodiments, the touchpad isa touch-sensitive area of the device that, unlike the touch screen, doesnot display visual output. The touchpad is, optionally, atouch-sensitive surface that is separate from touch-sensitive displaysystem 112 or an extension of the touch-sensitive surface formed by thetouch screen.

Device 100 also includes power system 162 for powering the variouscomponents. Power system 162 optionally includes a power managementsystem, one or more power sources (e.g., battery, alternating current(AC)), a recharging system, a power failure detection circuit, a powerconverter or inverter, a power status indicator (e.g., a light-emittingdiode (LED)) and any other components associated with the generation,management and distribution of power in portable devices.

Device 100 optionally also includes one or more optical sensors 164.FIG. 1A shows an optical sensor coupled with optical sensor controller158 in I/O subsystem 106. Optical sensor(s) 164 optionally includecharge-coupled device (CCD) or complementary metal-oxide semiconductor(CMOS) phototransistors. Optical sensor(s) 164 receive light from theenvironment, projected through one or more lens, and converts the lightto data representing an image. In conjunction with imaging module 143(also called a camera module), optical sensor(s) 164 optionally capturestill images and/or video. In some embodiments, an optical sensor islocated on the back of device 100, opposite touch-sensitive displaysystem 112 on the front of the device, so that the touch screen isenabled for use as a viewfinder for still and/or video imageacquisition. In some embodiments, another optical sensor is located onthe front of the device so that the user's image is obtained (e.g., forselfies, for videoconferencing while the user views the other videoconference participants on the touch screen, etc.).

Device 100 optionally also includes one or more contact intensitysensors 165. FIG. 1A shows a contact intensity sensor coupled withintensity sensor controller 159 in I/O subsystem 106. Contact intensitysensor(s) 165 optionally include one or more piezoresistive straingauges, capacitive force sensors, electric force sensors, piezoelectricforce sensors, optical force sensors, capacitive touch-sensitivesurfaces, or other intensity sensors (e.g., sensors used to measure theforce (or pressure) of a contact on a touch-sensitive surface). Contactintensity sensor(s) 165 receive contact intensity information (e.g.,pressure information or a proxy for pressure information) from theenvironment. In some embodiments, at least one contact intensity sensoris collocated with, or proximate to, a touch-sensitive surface (e.g.,touch-sensitive display system 112). In some embodiments, at least onecontact intensity sensor is located on the back of device 100, oppositetouch-screen display system 112 which is located on the front of device100.

Device 100 optionally also includes one or more proximity sensors 166.FIG. 1A shows proximity sensor 166 coupled with peripherals interface118. Alternately, proximity sensor 166 is coupled with input controller160 in I/O subsystem 106. In some embodiments, the proximity sensorturns off and disables touch-sensitive display system 112 when themultifunction device is placed near the user's ear (e.g., when the useris making a phone call).

Device 100 optionally also includes one or more tactile outputgenerators 163. FIG. 1A shows a tactile output generator coupled withhaptic feedback controller 161 in I/O subsystem 106. Tactile outputgenerator(s) 163 optionally include one or more electroacoustic devicessuch as speakers or other audio components and/or electromechanicaldevices that convert energy into linear motion such as a motor,solenoid, electroactive polymer, piezoelectric actuator, electrostaticactuator, or other tactile output generating component (e.g., acomponent that converts electrical signals into tactile outputs on thedevice). Tactile output generator(s) 163 receive tactile feedbackgeneration instructions from haptic feedback module 133 and generatestactile outputs on device 100 that are capable of being sensed by a userof device 100. In some embodiments, at least one tactile outputgenerator is collocated with, or proximate to, a touch-sensitive surface(e.g., touch-sensitive display system 112) and, optionally, generates atactile output by moving the touch-sensitive surface vertically (e.g.,in/out of a surface of device 100) or laterally (e.g., back and forth inthe same plane as a surface of device 100). In some embodiments, atleast one tactile output generator sensor is located on the back ofdevice 100, opposite touch-sensitive display system 112, which islocated on the front of device 100.

Device 100 optionally also includes one or more accelerometers 167,gyroscopes 168, and/or magnetometers 169 (e.g., as part of an inertialmeasurement unit (IMU)) for obtaining information concerning theposition (e.g., attitude) of the device. FIG. 1A shows sensors 167, 168,and 169 coupled with peripherals interface 118. Alternately, sensors167, 168, and 169 are, optionally, coupled with an input controller 160in I/O subsystem 106. In some embodiments, information is displayed onthe touch-screen display in a portrait view or a landscape view based onan analysis of data received from the one or more accelerometers. Device100 optionally includes a GPS (or GLONASS or other global navigationsystem) receiver (not shown) for obtaining information concerning thelocation of device 100.

In some embodiments, the software components stored in memory 102include operating system 126, communication module (or set ofinstructions) 128, contact/motion module (or set of instructions) 130,graphics module (or set of instructions) 132, haptic feedback module (orset of instructions) 133, text input module (or set of instructions)134, Global Positioning System (GPS) module (or set of instructions)135, and applications (or sets of instructions) 136. Furthermore, insome embodiments, memory 102 stores device/global internal state 157, asshown in FIGS. 1A and 3. Device/global internal state 157 includes oneor more of: active application state, indicating which applications, ifany, are currently active; display state, indicating what applications,views or other information occupy various regions of touch-sensitivedisplay system 112; sensor state, including information obtained fromthe device's various sensors and other input or control devices 116; andlocation and/or positional information concerning the device's locationand/or attitude.

Operating system 126 (e.g., iOS, Darwin, RTXC, LINUX, UNIX, OS X,WINDOWS, or an embedded operating system such as VxWorks) includesvarious software components and/or drivers for controlling and managinggeneral system tasks (e.g., memory management, storage device control,power management, etc.) and facilitates communication between varioushardware and software components.

Communication module 128 facilitates communication with other devicesover one or more external ports 124 and also includes various softwarecomponents for handling data received by RF circuitry 108 and/orexternal port 124. External port 124 (e.g., Universal Serial Bus (USB),FIREWIRE, etc.) is adapted for coupling directly to other devices orindirectly over a network (e.g., the Internet, wireless LAN, etc.). Insome embodiments, the external port is a multi-pin (e.g., 30-pin)connector that is the same as, or similar to and/or compatible with the30-pin connector used in some iPhone®, iPod Touch®, and iPad® devicesfrom Apple Inc. of Cupertino, Calif. In some embodiments, the externalport is a Lightning connector that is the same as, or similar to and/orcompatible with the Lightning connector used in some iPhone®, iPodTouch®, and iPad® devices from Apple Inc. of Cupertino, Calif.

Contact/motion module 130 optionally detects contact withtouch-sensitive display system 112 (in conjunction with displaycontroller 156) and other touch-sensitive devices (e.g., a touchpad orphysical click wheel). Contact/motion module 130 includes softwarecomponents for performing various operations related to detection ofcontact (e.g., by a finger or by a stylus), such as determining ifcontact has occurred (e.g., detecting a finger-down event), determiningan intensity of the contact (e.g., the force or pressure of the contactor a substitute for the force or pressure of the contact), determiningif there is movement of the contact and tracking the movement across thetouch-sensitive surface (e.g., detecting one or more finger-draggingevents), and determining if the contact has ceased (e.g., detecting afinger-up event or a break in contact). Contact/motion module 130receives contact data from the touch-sensitive surface. Determiningmovement of the point of contact, which is represented by a series ofcontact data, optionally includes determining speed (magnitude),velocity (magnitude and direction), and/or an acceleration (a change inmagnitude and/or direction) of the point of contact. These operationsare, optionally, applied to single contacts (e.g., one finger contactsor stylus contacts) or to multiple simultaneous contacts (e.g.,“multitouch”/multiple finger contacts and/or stylus contacts). In someembodiments, contact/motion module 130 and display controller 156 detectcontact on a touchpad.

Contact/motion module 130 optionally detects a gesture input by a user.Different gestures on the touch-sensitive surface have different contactpatterns (e.g., different motions, timings, and/or intensities ofdetected contacts). Thus, a gesture is, optionally, detected bydetecting a particular contact pattern. For example, detecting a fingertap gesture includes detecting a finger-down event followed by detectinga finger-up (lift off) event at the same position (or substantially thesame position) as the finger-down event (e.g., at the position of anicon). As another example, detecting a finger swipe gesture on thetouch-sensitive surface includes detecting a finger-down event followedby detecting one or more finger-dragging events, and subsequentlyfollowed by detecting a finger-up (lift off) event. Similarly, tap,swipe, drag, and other gestures are optionally detected for a stylus bydetecting a particular contact pattern for the stylus.

Graphics module 132 includes various known software components forrendering and displaying graphics on touch-sensitive display system 112or other display, including components for changing the visual impact(e.g., brightness, transparency, saturation, contrast or other visualproperty) of graphics that are displayed. As used herein, the term“graphics” includes any object that can be displayed to a user,including without limitation text, web pages, icons (such asuser-interface objects including soft keys), digital images, videos,animations and the like.

In some embodiments, graphics module 132 stores data representinggraphics to be used. Each graphic is, optionally, assigned acorresponding code. Graphics module 132 receives, from applicationsetc., one or more codes specifying graphics to be displayed along with,if necessary, coordinate data and other graphic property data, and thengenerates screen image data to output to display controller 156.

Haptic feedback module 133 includes various software components forgenerating instructions used by tactile output generator(s) 163 toproduce tactile outputs at one or more locations on device 100 inresponse to user interactions with device 100.

Text input module 134, which is, optionally, a component of graphicsmodule 132, provides soft keyboards for entering text in variousapplications (e.g., contacts 137, e-mail client 140, IM 141, browser147, and any other application that needs text input).

GPS module 135 determines the location of the device and provides thisinformation for use in various applications (e.g., to telephone 138 foruse in location-based dialing, to camera 143 as picture/video metadata,and to applications that provide location-based services such as weatherwidgets, local yellow page widgets, and map/navigation widgets).

Applications 136 optionally include the following modules (or sets ofinstructions), or a subset or superset thereof:

-   -   contacts module 137 (sometimes called an address book or contact        list);    -   telephone module 138;    -   video conference module 139;    -   e-mail client module 140;    -   instant messaging (IM) module 141;    -   workout support module 142;    -   camera module 143 for still and/or video images;    -   image management module 144;    -   browser module 147;    -   calendar module 148;    -   widget modules 149, which optionally include one or more of:        weather widget 149-1, stocks widget 149-2, calculator widget        149-3, alarm clock widget 149-4, dictionary widget 149-5, and        other widgets obtained by the user, as well as user-created        widgets 149-6;    -   widget creator module 150 for making user-created widgets 149-6;    -   search module 151;    -   video and music player module 152, which is, optionally, made up        of a video player module and a music player module;    -   notes module 153;    -   map module 154; and/or    -   online video module 155.

Examples of other applications 136 that are, optionally, stored inmemory 102 include other word processing applications, other imageediting applications, drawing applications, presentation applications,JAVA-enabled applications, encryption, digital rights management, voicerecognition, and voice replication.

In conjunction with touch-sensitive display system 112, displaycontroller 156, contact module 130, graphics module 132, and text inputmodule 134, contacts module 137 includes executable instructions tomanage an address book or contact list (e.g., stored in applicationinternal state 192 of contacts module 137 in memory 102 or memory 370),including: adding name(s) to the address book; deleting name(s) from theaddress book; associating telephone number(s), e-mail address(es),physical address(es) or other information with a name; associating animage with a name; categorizing and sorting names; providing telephonenumbers and/or e-mail addresses to initiate and/or facilitatecommunications by telephone 138, video conference 139, e-mail client140, or IM 141; and so forth.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111,microphone 113, touch-sensitive display system 112, display controller156, contact module 130, graphics module 132, and text input module 134,telephone module 138 includes executable instructions to enter asequence of characters corresponding to a telephone number, access oneor more telephone numbers in address book 137, modify a telephone numberthat has been entered, dial a respective telephone number, conduct aconversation and disconnect or hang up when the conversation iscompleted. As noted above, the wireless communication optionally usesany of a plurality of communications standards, protocols andtechnologies.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111,microphone 113, touch-sensitive display system 112, display controller156, optical sensor(s) 164, optical sensor controller 158, contactmodule 130, graphics module 132, text input module 134, contact list137, and telephone module 138, video conference module 139 includesexecutable instructions to initiate, conduct, and terminate a videoconference between a user and one or more other participants inaccordance with user instructions.

In conjunction with RF circuitry 108, touch-sensitive display system112, display controller 156, contact module 130, graphics module 132,and text input module 134, e-mail client module 140 includes executableinstructions to create, send, receive, and manage e-mail in response touser instructions. In conjunction with image management module 144,e-mail client module 140 makes it very easy to create and send e-mailswith still or video images taken with camera module 143.

In conjunction with RF circuitry 108, touch-sensitive display system112, display controller 156, contact module 130, graphics module 132,and text input module 134, the instant messaging module 141 includesexecutable instructions to enter a sequence of characters correspondingto an instant message, to modify previously entered characters, totransmit a respective instant message (for example, using a ShortMessage Service (SMS) or Multimedia Message Service (MMS) protocol fortelephony-based instant messages or using XMPP, SIMPLE, Apple PushNotification Service (APNs) or IMPS for Internet-based instantmessages), to receive instant messages and to view received instantmessages. In some embodiments, transmitted and/or received instantmessages optionally include graphics, photos, audio files, video filesand/or other attachments as are supported in a MMS and/or an EnhancedMessaging Service (EMS). As used herein, “instant messaging” refers toboth telephony-based messages (e.g., messages sent using SMS or MMS) andInternet-based messages (e.g., messages sent using XMPP, SIMPLE, APNs,or IMPS).

In conjunction with RF circuitry 108, touch-sensitive display system112, display controller 156, contact module 130, graphics module 132,text input module 134, GPS module 135, map module 154, and video andmusic player module 152, workout support module 142 includes executableinstructions to create workouts (e.g., with time, distance, and/orcalorie burning goals); communicate with workout sensors (in sportsdevices and smart watches); receive workout sensor data; calibratesensors used to monitor a workout; select and play music for a workout;and display, store and transmit workout data.

In conjunction with touch-sensitive display system 112, displaycontroller 156, optical sensor(s) 164, optical sensor controller 158,contact module 130, graphics module 132, and image management module144, camera module 143 includes executable instructions to capture stillimages or video (including a video stream) and store them into memory102, modify characteristics of a still image or video, and/or delete astill image or video from memory 102.

In conjunction with touch-sensitive display system 112, displaycontroller 156, contact module 130, graphics module 132, text inputmodule 134, and camera module 143, image management module 144 includesexecutable instructions to arrange, modify (e.g., edit), or otherwisemanipulate, label, delete, present (e.g., in a digital slide show oralbum), and store still and/or video images.

In conjunction with RF circuitry 108, touch-sensitive display system112, display system controller 156, contact module 130, graphics module132, and text input module 134, browser module 147 includes executableinstructions to browse the Internet in accordance with userinstructions, including searching, linking to, receiving, and displayingweb pages or portions thereof, as well as attachments and other fileslinked to web pages.

In conjunction with RF circuitry 108, touch-sensitive display system112, display system controller 156, contact module 130, graphics module132, text input module 134, e-mail client module 140, and browser module147, calendar module 148 includes executable instructions to create,display, modify, and store calendars and data associated with calendars(e.g., calendar entries, to do lists, etc.) in accordance with userinstructions.

In conjunction with RF circuitry 108, touch-sensitive display system112, display system controller 156, contact module 130, graphics module132, text input module 134, and browser module 147, widget modules 149are mini-applications that are, optionally, downloaded and used by auser (e.g., weather widget 149-1, stocks widget 149-2, calculator widget149-3, alarm clock widget 149-4, and dictionary widget 149-5) or createdby the user (e.g., user-created widget 149-6). In some embodiments, awidget includes an HTML (Hypertext Markup Language) file, a CSS(Cascading Style Sheets) file, and a JavaScript file. In someembodiments, a widget includes an XML (Extensible Markup Language) fileand a JavaScript file (e.g., Yahoo! Widgets).

In conjunction with RF circuitry 108, touch-sensitive display system112, display system controller 156, contact module 130, graphics module132, text input module 134, and browser module 147, the widget creatormodule 150 includes executable instructions to create widgets (e.g.,turning a user-specified portion of a web page into a widget).

In conjunction with touch-sensitive display system 112, display systemcontroller 156, contact module 130, graphics module 132, and text inputmodule 134, search module 151 includes executable instructions to searchfor text, music, sound, image, video, and/or other files in memory 102that match one or more search criteria (e.g., one or more user-specifiedsearch terms) in accordance with user instructions.

In conjunction with touch-sensitive display system 112, display systemcontroller 156, contact module 130, graphics module 132, audio circuitry110, speaker 111, RF circuitry 108, and browser module 147, video andmusic player module 152 includes executable instructions that allow theuser to download and play back recorded music and other sound filesstored in one or more file formats, such as MP3 or AAC files, andexecutable instructions to display, present or otherwise play backvideos (e.g., on touch-sensitive display system 112, or on an externaldisplay connected wirelessly or via external port 124). In someembodiments, device 100 optionally includes the functionality of an MP3player, such as an iPod (trademark of Apple Inc.).

In conjunction with touch-sensitive display system 112, displaycontroller 156, contact module 130, graphics module 132, and text inputmodule 134, notes module 153 includes executable instructions to createand manage notes, to do lists, and the like in accordance with userinstructions.

In conjunction with RF circuitry 108, touch-sensitive display system112, display system controller 156, contact module 130, graphics module132, text input module 134, GPS module 135, and browser module 147, mapmodule 154 includes executable instructions to receive, display, modify,and store maps and data associated with maps (e.g., driving directions;data on stores and other points of interest at or near a particularlocation; and other location-based data) in accordance with userinstructions.

In conjunction with touch-sensitive display system 112, display systemcontroller 156, contact module 130, graphics module 132, audio circuitry110, speaker 111, RF circuitry 108, text input module 134, e-mail clientmodule 140, and browser module 147, online video module 155 includesexecutable instructions that allow the user to access, browse, receive(e.g., by streaming and/or download), play back (e.g., on the touchscreen 112, or on an external display connected wirelessly or viaexternal port 124), send an e-mail with a link to a particular onlinevideo, and otherwise manage online videos in one or more file formats,such as H.264. In some embodiments, instant messaging module 141, ratherthan e-mail client module 140, is used to send a link to a particularonline video.

Each of the above identified modules and applications correspond to aset of executable instructions for performing one or more functionsdescribed above and the methods described in this application (e.g., thecomputer-implemented methods and other information processing methodsdescribed herein). These modules (i.e., sets of instructions) need notbe implemented as separate software programs, procedures or modules, andthus various subsets of these modules are, optionally, combined orotherwise re-arranged in various embodiments. In some embodiments,memory 102 optionally stores a subset of the modules and data structuresidentified above. Furthermore, memory 102 optionally stores additionalmodules and data structures not described above.

In some embodiments, device 100 is a device where operation of apredefined set of functions on the device is performed exclusivelythrough a touch screen and/or a touchpad. By using a touch screen and/ora touchpad as the primary input control device for operation of device100, the number of physical input control devices (such as push buttons,dials, and the like) on device 100 is, optionally, reduced.

The predefined set of functions that are performed exclusively through atouch screen and/or a touchpad optionally include navigation betweenuser interfaces. In some embodiments, the touchpad, when touched by theuser, navigates device 100 to a main, home, or root menu from any userinterface that is displayed on device 100. In such embodiments, a “menubutton” is implemented using a touchpad. In some other embodiments, themenu button is a physical push button or other physical input controldevice instead of a touchpad.

FIG. 1B is a block diagram illustrating example components for eventhandling in accordance with some embodiments. In some embodiments,memory 102 (in FIG. 1A) or 370 (FIG. 3) includes event sorter 170 (e.g.,in operating system 126) and a respective application 136-1 (e.g., anyof the aforementioned applications 136, 137-155, 380-390).

Event sorter 170 receives event information and determines theapplication 136-1 and application view 191 of application 136-1 to whichto deliver the event information. Event sorter 170 includes eventmonitor 171 and event dispatcher module 174. In some embodiments,application 136-1 includes application internal state 192, whichindicates the current application view(s) displayed on touch-sensitivedisplay system 112 when the application is active or executing. In someembodiments, device/global internal state 157 is used by event sorter170 to determine which application(s) is (are) currently active, andapplication internal state 192 is used by event sorter 170 to determineapplication views 191 to which to deliver event information.

In some embodiments, application internal state 192 includes additionalinformation, such as one or more of: resume information to be used whenapplication 136-1 resumes execution, user interface state informationthat indicates information being displayed or that is ready for displayby application 136-1, a state queue for enabling the user to go back toa prior state or view of application 136-1, and a redo/undo queue ofprevious actions taken by the user.

Event monitor 171 receives event information from peripherals interface118. Event information includes information about a sub-event (e.g., auser touch on touch-sensitive display system 112, as part of amulti-touch gesture). Peripherals interface 118 transmits information itreceives from I/O subsystem 106 or a sensor, such as proximity sensor166, accelerometer(s) 167, gyroscope(s) 168, magnetometer(s) 169, and/ormicrophone 113 (through audio circuitry 110). Information thatperipherals interface 118 receives from I/O subsystem 106 includesinformation from touch-sensitive display system 112 or a touch-sensitivesurface.

In some embodiments, event monitor 171 sends requests to the peripheralsinterface 118 at predetermined intervals. In response, peripheralsinterface 118 transmits event information. In other embodiments,peripheral interface 118 transmits event information only when there isa significant event (e.g., receiving an input above a predeterminednoise threshold and/or for more than a predetermined duration).

In some embodiments, event sorter 170 also includes a hit viewdetermination module 172 and/or an active event recognizer determinationmodule 173.

Hit view determination module 172 provides software procedures fordetermining where a sub-event has taken place within one or more views,when touch-sensitive display system 112 displays more than one view.Views are made up of controls and other elements that a user can see onthe display.

Another aspect of the user interface associated with an application is aset of views, sometimes herein called application views or userinterface windows, in which information is displayed and touch-basedgestures occur. The application views (of a respective application) inwhich a touch is detected optionally correspond to programmatic levelswithin a programmatic or view hierarchy of the application. For example,the lowest level view in which a touch is detected is, optionally,called the hit view, and the set of events that are recognized as properinputs are, optionally, determined based, at least in part, on the hitview of the initial touch that begins a touch-based gesture.

Hit view determination module 172 receives information related tosub-events of a touch-based gesture. When an application has multipleviews organized in a hierarchy, hit view determination module 172identifies a hit view as the lowest view in the hierarchy which shouldhandle the sub-event. In most circumstances, the hit view is the lowestlevel view in which an initiating sub-event occurs (i.e., the firstsub-event in the sequence of sub-events that form an event or potentialevent). Once the hit view is identified by the hit view determinationmodule, the hit view typically receives all sub-events related to thesame touch or input source for which it was identified as the hit view.

Active event recognizer determination module 173 determines which viewor views within a view hierarchy should receive a particular sequence ofsub-events. In some embodiments, active event recognizer determinationmodule 173 determines that only the hit view should receive a particularsequence of sub-events. In other embodiments, active event recognizerdetermination module 173 determines that all views that include thephysical location of a sub-event are actively involved views, andtherefore determines that all actively involved views should receive aparticular sequence of sub-events. In other embodiments, even if touchsub-events were entirely confined to the area associated with oneparticular view, views higher in the hierarchy would still remain asactively involved views.

Event dispatcher module 174 dispatches the event information to an eventrecognizer (e.g., event recognizer 180). In embodiments including activeevent recognizer determination module 173, event dispatcher module 174delivers the event information to an event recognizer determined byactive event recognizer determination module 173. In some embodiments,event dispatcher module 174 stores in an event queue the eventinformation, which is retrieved by a respective event receiver module182.

In some embodiments, operating system 126 includes event sorter 170.Alternatively, application 136-1 includes event sorter 170. In yet otherembodiments, event sorter 170 is a stand-alone module, or a part ofanother module stored in memory 102, such as contact/motion module 130.

In some embodiments, application 136-1 includes a plurality of eventhandlers 190 and one or more application views 191, each of whichincludes instructions for handling touch events that occur within arespective view of the application's user interface. Each applicationview 191 of the application 136-1 includes one or more event recognizers180. Typically, a respective application view 191 includes a pluralityof event recognizers 180. In other embodiments, one or more of eventrecognizers 180 are part of a separate module, such as a user interfacekit (not shown) or a higher level object from which application 136-1inherits methods and other properties. In some embodiments, a respectiveevent handler 190 includes one or more of: data updater 176, objectupdater 177, GUI updater 178, and/or event data 179 received from eventsorter 170. Event handler 190 optionally utilizes or calls data updater176, object updater 177 or GUI updater 178 to update the applicationinternal state 192. Alternatively, one or more of the application views191 includes one or more respective event handlers 190. Also, in someembodiments, one or more of data updater 176, object updater 177, andGUI updater 178 are included in a respective application view 191.

A respective event recognizer 180 receives event information (e.g.,event data 179) from event sorter 170, and identifies an event from theevent information. Event recognizer 180 includes event receiver 182 andevent comparator 184. In some embodiments, event recognizer 180 alsoincludes at least a subset of: metadata 183, and event deliveryinstructions 188 (which optionally include sub-event deliveryinstructions).

Event receiver 182 receives event information from event sorter 170. Theevent information includes information about a sub-event, for example, atouch or a touch movement. Depending on the sub-event, the eventinformation also includes additional information, such as location ofthe sub-event. When the sub-event concerns motion of a touch, the eventinformation optionally also includes speed and direction of thesub-event. In some embodiments, events include rotation of the devicefrom one orientation to another (e.g., from a portrait orientation to alandscape orientation, or vice versa), and the event informationincludes corresponding information about the current orientation (alsocalled device attitude) of the device.

Event comparator 184 compares the event information to predefined eventor sub-event definitions and, based on the comparison, determines anevent or sub-event, or determines or updates the state of an event orsub-event. In some embodiments, event comparator 184 includes eventdefinitions 186. Event definitions 186 contain definitions of events(e.g., predefined sequences of sub-events), for example, event 1(187-1), event 2 (187-2), and others. In some embodiments, sub-events ina respective event, such as event 1 (187-1) or event 2 (187-2), include,for example, touch begin, touch end, touch movement, touch cancellation,and multiple touching. In one example, the definition for event 1(187-1) is a double tap on a displayed object. The double tap, forexample, comprises a first touch (touch begin) on the displayed objectfor a predetermined phase, a first lift-off (touch end) for apredetermined phase, a second touch (touch begin) on the displayedobject for a predetermined phase, and a second lift-off (touch end) fora predetermined phase. In another example, the definition for event 2(187-2) is a dragging on a displayed object. The dragging, for example,comprises a touch (or contact) on the displayed object for apredetermined phase, a movement of the touch across touch-sensitivedisplay system 112, and lift-off of the touch (touch end). In someembodiments, the event also includes information for one or moreassociated event handlers 190.

In some embodiments, the event definition for a respective event, suchas event 1 (187-1) or event 2 (187-2), includes a definition of an eventfor a respective user-interface object. In some embodiments, eventcomparator 184 performs a hit test to determine which user-interfaceobject is associated with a sub-event. For example, in an applicationview in which three user-interface objects are displayed ontouch-sensitive display system 112, when a touch is detected ontouch-sensitive display system 112, event comparator 184 performs a hittest to determine which of the three user-interface objects isassociated with the touch (sub-event). If each displayed object isassociated with a respective event handler 190, the event comparatoruses the result of the hit test to determine which event handler 190should be activated. For example, event comparator 184 selects an eventhandler associated with the sub-event and the object triggering the hittest.

In some embodiments, the definition for a respective event, such asevent 1 (187-1) or event 2 (187-2), also includes delayed actions thatdelay delivery of the event information until after it has beendetermined whether the sequence of sub-events does or does notcorrespond to the event recognizer's event type.

When a respective event recognizer 180 determines that the series ofsub-events do not match any of the events in event definitions 186, therespective event recognizer 180 enters an event impossible, eventfailed, or event ended state, after which it disregards subsequentsub-events of the touch-based gesture. In this situation, other eventrecognizers, if any, that remain active for the hit view continue totrack and process sub-events of an ongoing touch-based gesture.

In some embodiments, a respective event recognizer 180 includes metadata183 with configurable properties, flags, and/or lists that indicate howthe event delivery system should perform sub-event delivery to activelyinvolved event recognizers. In some embodiments, metadata 183 includesconfigurable properties, flags, and/or lists that indicate how eventrecognizers interact, or are enabled to interact, with one another. Insome embodiments, metadata 183 includes configurable properties, flags,and/or lists that indicate whether sub-events are delivered to varyinglevels in the view or programmatic hierarchy.

In some embodiments, a respective event recognizer 180 activates eventhandler 190 associated with an event when one or more particularsub-events of an event are recognized. In some embodiments, a respectiveevent recognizer 180 delivers event information associated with theevent to event handler 190. Activating an event handler 190 is distinctfrom sending (and deferred sending) sub-events to a respective hit view.In some embodiments, event recognizer 180 throws a flag associated withthe recognized event, and event handler 190 associated with the flagcatches the flag and performs a predefined process.

In some embodiments, event delivery instructions 188 include sub-eventdelivery instructions that deliver event information about a sub-eventwithout activating an event handler. Instead, the sub-event deliveryinstructions deliver event information to event handlers associated withthe series of sub-events or to actively involved views. Event handlersassociated with the series of sub-events or with actively involved viewsreceive the event information and perform a predetermined process.

In some embodiments, data updater 176 creates and updates data used inapplication 136-1. For example, data updater 176 updates the telephonenumber used in contacts module 137, or stores a video file used in videoplayer module 145. In some embodiments, object updater 177 creates andupdates objects used in application 136-1. For example, object updater177 creates a new user-interface object or updates the position of auser-interface object. GUI updater 178 updates the GUI. For example, GUIupdater 178 prepares display information and sends it to graphics module132 for display on a touch-sensitive display.

In some embodiments, event handler(s) 190 includes or has access to dataupdater 176, object updater 177, and GUI updater 178. In someembodiments, data updater 176, object updater 177, and GUI updater 178are included in a single module of a respective application 136-1 orapplication view 191. In other embodiments, they are included in two ormore software modules.

It shall be understood that the foregoing discussion regarding eventhandling of user touches on touch-sensitive displays also applies toother forms of user inputs to operate multifunction devices 100 withinput-devices, not all of which are initiated on touch screens. Forexample, mouse movement and mouse button presses, optionally coordinatedwith single or multiple keyboard presses or holds; contact movementssuch as taps, drags, scrolls, etc., on touch-pads; pen stylus inputs;movement of the device; oral instructions; detected eye movements;biometric inputs; and/or any combination thereof are optionally utilizedas inputs corresponding to sub-events which define an event to berecognized.

FIG. 2 illustrates a portable multifunction device 100 having a touchscreen (e.g., touch-sensitive display system 112, FIG. 1A) in accordancewith some embodiments. The touch screen optionally displays one or moregraphics within user interface (UI) 200. In this embodiment, as well asothers described below, a user is enabled to select one or more of thegraphics by making a gesture on the graphics, for example, with one ormore fingers 202 (not drawn to scale in the figure) or one or morestyluses 203 (not drawn to scale in the figure). In some embodiments,selection of one or more graphics occurs when the user breaks contactwith the one or more graphics. In some embodiments, the gestureoptionally includes one or more taps, one or more swipes (from left toright, right to left, upward and/or downward) and/or a rolling of afinger (from right to left, left to right, upward and/or downward) thathas made contact with device 100. In some implementations orcircumstances, inadvertent contact with a graphic does not select thegraphic. For example, a swipe gesture that sweeps over an applicationicon optionally does not select the corresponding application when thegesture corresponding to selection is a tap.

Device 100 optionally also includes one or more physical buttons, suchas “home” or menu button 204. As described previously, menu button 204is, optionally, used to navigate to any application 136 in a set ofapplications that are, optionally executed on device 100. Alternatively,in some embodiments, the menu button is implemented as a soft key in aGUI displayed on the touch-screen display.

In some embodiments, device 100 includes the touch-screen display, menubutton 204, push button 206 for powering the device on/off and lockingthe device, volume adjustment button(s) 208, Subscriber Identity Module(SIM) card slot 210, head set jack 212, and docking/charging externalport 124. Push button 206 is, optionally, used to turn the power on/offon the device by depressing the button and holding the button in thedepressed state for a predefined time interval; to lock the device bydepressing the button and releasing the button before the predefinedtime interval has elapsed; and/or to unlock the device or initiate anunlock process. In some embodiments, device 100 also accepts verbalinput for activation or deactivation of some functions throughmicrophone 113. Device 100 also, optionally, includes one or morecontact intensity sensors 165 for detecting intensity of contacts ontouch-sensitive display system 112 and/or one or more tactile outputgenerators 163 for generating tactile outputs for a user of device 100.

FIG. 3 is a block diagram of an example multifunction device with adisplay and a touch-sensitive surface in accordance with someembodiments. Device 300 need not be portable. In some embodiments,device 300 is a laptop computer, a desktop computer, a tablet computer,a multimedia player device, a navigation device, an educational device(such as a child's learning toy), a gaming system, or a control device(e.g., a home or industrial controller). Device 300 typically includesone or more processing units (CPU's) 310, one or more network or othercommunications interfaces 360, memory 370, and one or more communicationbuses 320 for interconnecting these components. Communication buses 320optionally include circuitry (sometimes called a chipset) thatinterconnects and controls communications between system components.Device 300 includes input/output (I/O) interface 330 comprising display340, which is typically a touch-screen display. I/O interface 330 alsooptionally includes a keyboard and/or mouse (or other pointing device)350 and touchpad 355, tactile output generator 357 for generatingtactile outputs on device 300 (e.g., similar to tactile outputgenerator(s) 163 described above with reference to FIG. 1A), sensors 359(e.g., touch-sensitive, optical, contact intensity, proximity,acceleration, attitude, and/or magnetic sensors similar to sensors 112,164, 165, 166, 167, 168, and 169 described above with reference to FIG.1A). Memory 370 includes high-speed random access memory, such as DRAM,SRAM, DDR RAM or other random access solid state memory devices; andoptionally includes non-volatile memory, such as one or more magneticdisk storage devices, optical disk storage devices, flash memorydevices, or other non-volatile solid state storage devices. Memory 370optionally includes one or more storage devices remotely located fromCPU(s) 310. In some embodiments, memory 370 stores programs, modules,and data structures analogous to the programs, modules, and datastructures stored in memory 102 of portable multifunction device 100(FIG. 1A), or a subset thereof. Furthermore, memory 370 optionallystores additional programs, modules, and data structures not present inmemory 102 of portable multifunction device 100. For example, memory 370of device 300 optionally stores drawing module 380, presentation module382, word processing module 384, website creation module 386, diskauthoring module 388, and/or spreadsheet module 390, while memory 102 ofportable multifunction device 100 (FIG. 1A) optionally does not storethese modules.

Each of the above identified elements in FIG. 3 are, optionally, storedin one or more of the previously mentioned memory devices. Each of theabove identified modules corresponds to a set of instructions forperforming a function described above. The above identified modules orprograms (i.e., sets of instructions) need not be implemented asseparate software programs, procedures or modules, and thus varioussubsets of these modules are, optionally, combined or otherwisere-arranged in various embodiments. In some embodiments, memory 370optionally stores a subset of the modules and data structures identifiedabove. Furthermore, memory 370 optionally stores additional modules anddata structures not described above.

Attention is now directed toward embodiments of user interfaces (“UI”)that are, optionally, implemented on portable multifunction device 100.

FIG. 4A illustrates an example user interface for a menu of applicationson portable multifunction device 100 in accordance with someembodiments. Similar user interfaces are, optionally, implemented ondevice 300. In some embodiments, user interface 400 includes thefollowing elements, or a subset or superset thereof:

-   -   Signal strength indicator(s) 402 for wireless communication(s),        such as cellular and Wi-Fi signals;    -   Time 404;    -   Bluetooth indicator 405;    -   Battery status indicator 406;    -   Tray 408 with icons for frequently used applications, such as:        -   Icon 416 for telephone module 138, labeled “Phone,” which            optionally includes an indicator 414 of the number of missed            calls or voicemail messages;        -   Icon 418 for e-mail client module 140, labeled “Mail,” which            optionally includes an indicator 410 of the number of unread            e-mails;        -   Icon 420 for browser module 147, labeled “Browser”; and        -   Icon 422 for video and music player module 152, also            referred to as iPod (trademark of Apple Inc.) module 152,            labeled “iPod”; and    -   Icons for other applications, such as:        -   Icon 424 for IM module 141, labeled “Text”;        -   Icon 426 for calendar module 148, labeled “Calendar”;        -   Icon 428 for image management module 144, labeled “Photos”;        -   Icon 430 for camera module 143, labeled “Camera”;        -   Icon 432 for online video module 155, labeled “Online            Video”;        -   Icon 434 for stocks widget 149-2, labeled “Stocks”;        -   Icon 436 for map module 154, labeled “Map”;        -   Icon 438 for weather widget 149-1, labeled “Weather”;        -   Icon 440 for alarm clock widget 169-6, labeled “Clock”;        -   Icon 442 for workout support module 142, labeled “Workout            Support”;        -   Icon 444 for notes module 153, labeled “Notes”; and        -   Icon 446 for a settings application or module, which            provides access to settings for device 100 and its various            applications 136.

It should be noted that the icon labels illustrated in FIG. 4A aremerely examples. For example, in some embodiments, icon 422 for videoand music player module 152 is labeled “Music” or “Music Player.” Otherlabels are, optionally, used for various application icons. In someembodiments, a label for a respective application icon includes a nameof an application corresponding to the respective application icon. Insome embodiments, a label for a particular application icon is distinctfrom a name of an application corresponding to the particularapplication icon.

FIG. 4B illustrates an example user interface on a device (e.g., device300, FIG. 3) with a touch-sensitive surface 451 (e.g., a tablet ortouchpad 355, FIG. 3) that is separate from the display 450. Device 300also, optionally, includes one or more contact intensity sensors (e.g.,one or more of sensors 359) for detecting intensity of contacts ontouch-sensitive surface 451 and/or one or more tactile output generators359 for generating tactile outputs for a user of device 300.

FIG. 4B illustrates an example user interface on a device (e.g., device300, FIG. 3) with a touch-sensitive surface 451 (e.g., a tablet ortouchpad 355, FIG. 3) that is separate from the display 450. Althoughmany of the examples that follow will be given with reference to inputson touch screen display 112 (where the touch sensitive surface and thedisplay are combined), in some embodiments, the device detects inputs ona touch-sensitive surface that is separate from the display, as shown inFIG. 4B. In some embodiments, the touch-sensitive surface (e.g., 451 inFIG. 4B) has a primary axis (e.g., 452 in FIG. 4B) that corresponds to aprimary axis (e.g., 453 in FIG. 4B) on the display (e.g., 450). Inaccordance with these embodiments, the device detects contacts (e.g.,460 and 462 in FIG. 4B) with the touch-sensitive surface 451 atlocations that correspond to respective locations on the display (e.g.,in FIG. 4B, 460 corresponds to 468 and 462 corresponds to 470). In thisway, user inputs (e.g., contacts 460 and 462, and movements thereof)detected by the device on the touch-sensitive surface (e.g., 451 in FIG.4B) are used by the device to manipulate the user interface on thedisplay (e.g., 450 in FIG. 4B) of the multifunction device when thetouch-sensitive surface is separate from the display. It should beunderstood that similar methods are, optionally, used for other userinterfaces described herein.

Additionally, while the following examples are given primarily withreference to finger inputs (e.g., finger contacts, finger tap gestures,finger swipe gestures, etc.), it should be understood that, in someembodiments, one or more of the finger inputs are replaced with inputfrom another input device (e.g., a mouse based input or a stylus input).For example, a swipe gesture is, optionally, replaced with a mouse click(e.g., instead of a contact) followed by movement of the cursor alongthe path of the swipe (e.g., instead of movement of the contact). Asanother example, a tap gesture is, optionally, replaced with a mouseclick while the cursor is located over the location of the tap gesture(e.g., instead of detection of the contact followed by ceasing to detectthe contact). Similarly, when multiple user inputs are simultaneouslydetected, it should be understood that multiple computer mice are,optionally, used simultaneously, or a mouse and finger contacts are,optionally, used simultaneously.

As used herein, the term “focus selector” refers to an input elementthat indicates a current part of a user interface with which a user isinteracting. In some implementations that include a cursor or otherlocation marker, the cursor acts as a “focus selector,” so that when aninput (e.g., a press input) is detected on a touch-sensitive surface(e.g., touchpad 355 in FIG. 3 or touch-sensitive surface 451 in FIG. 4B)while the cursor is over a particular user interface element (e.g., abutton, window, slider or other user interface element), the particularuser interface element is adjusted in accordance with the detectedinput. In some implementations that include a touch-screen display(e.g., touch-sensitive display system 112 in FIG. 1A or the touch screenin FIG. 4A) that enables direct interaction with user interface elementson the touch-screen display, a detected contact on the touch-screen actsas a “focus selector,” so that when an input (e.g., a press input by thecontact) is detected on the touch-screen display at a location of aparticular user interface element (e.g., a button, window, slider orother user interface element), the particular user interface element isadjusted in accordance with the detected input. In some implementations,focus is moved from one region of a user interface to another region ofthe user interface without corresponding movement of a cursor ormovement of a contact on a touch-screen display (e.g., by using a tabkey or arrow keys to move focus from one button to another button); inthese implementations, the focus selector moves in accordance withmovement of focus between different regions of the user interface.Without regard to the specific form taken by the focus selector, thefocus selector is generally the user interface element (or contact on atouch-screen display) that is controlled by the user so as tocommunicate the user's intended interaction with the user interface(e.g., by indicating, to the device, the element of the user interfacewith which the user is intending to interact). For example, the locationof a focus selector (e.g., a cursor, a contact, or a selection box) overa respective button while a press input is detected on thetouch-sensitive surface (e.g., a touchpad or touch screen) will indicatethat the user is intending to activate the respective button (as opposedto other user interface elements shown on a display of the device).

As used in the specification and claims, the term “intensity” of acontact on a touch-sensitive surface refers to the force or pressure(force per unit area) of a contact (e.g., a finger contact or a styluscontact) on the touch-sensitive surface, or to a substitute (proxy) forthe force or pressure of a contact on the touch-sensitive surface. Theintensity of a contact has a range of values that includes at least fourdistinct values and more typically includes hundreds of distinct values(e.g., at least 256). Intensity of a contact is, optionally, determined(or measured) using various approaches and various sensors orcombinations of sensors. For example, one or more force sensorsunderneath or adjacent to the touch-sensitive surface are, optionally,used to measure force at various points on the touch-sensitive surface.In some implementations, force measurements from multiple force sensorsare combined (e.g., a weighted average or a sum) to determine anestimated force of a contact. Similarly, a pressure-sensitive tip of astylus is, optionally, used to determine a pressure of the stylus on thetouch-sensitive surface. Alternatively, the size of the contact areadetected on the touch-sensitive surface and/or changes thereto, thecapacitance of the touch-sensitive surface proximate to the contactand/or changes thereto, and/or the resistance of the touch-sensitivesurface proximate to the contact and/or changes thereto are, optionally,used as a substitute for the force or pressure of the contact on thetouch-sensitive surface. In some implementations, the substitutemeasurements for contact force or pressure are used directly todetermine whether an intensity threshold has been exceeded (e.g., theintensity threshold is described in units corresponding to thesubstitute measurements). In some implementations, the substitutemeasurements for contact force or pressure are converted to an estimatedforce or pressure and the estimated force or pressure is used todetermine whether an intensity threshold has been exceeded (e.g., theintensity threshold is a pressure threshold measured in units ofpressure). Using the intensity of a contact as an attribute of a userinput allows for user access to additional device functionality that mayotherwise not be readily accessible by the user on a reduced-size devicewith limited real estate for displaying affordances (e.g., on atouch-sensitive display) and/or receiving user input (e.g., via atouch-sensitive display, a touch-sensitive surface, or aphysical/mechanical control such as a knob or a button).

In some embodiments, contact/motion module 130 and/or 430 uses a set ofone or more intensity thresholds to determine whether an operation hasbeen performed by a user (e.g., to determine whether a user has“clicked” on an icon). In some embodiments, at least a subset of theintensity thresholds is determined in accordance with softwareparameters (e.g., the intensity thresholds are not determined by theactivation thresholds of particular physical actuators and can beadjusted without changing the physical hardware of device 100). Forexample, a mouse “click” threshold of a trackpad or touch-screen displaycan be set to any of a large range of predefined threshold valueswithout changing the trackpad or touch-screen display hardware.Additionally, in some embodiments, a user of the device is provided withsoftware settings for adjusting one or more of the set of intensitythresholds (e.g., by adjusting individual intensity thresholds and/or byadjusting a plurality of intensity thresholds at once with asystem-level click “intensity” parameter).

As used in the specification and claims, the term “characteristicintensity” of a contact refers to a characteristic of the contact basedon one or more intensities of the contact. In some embodiments, thecharacteristic intensity is based on multiple intensity samples. Thecharacteristic intensity is, optionally, based on a predefined number ofintensity samples, or a set of intensity samples collected during apredetermined time period (e.g., 0.05, 0.1, 0.2, 0.5, 1, 2, 5, 10seconds) relative to a predefined event (e.g., after detecting thecontact, prior to detecting liftoff of the contact, before or afterdetecting a start of movement of the contact, prior to detecting an endof the contact, before or after detecting an increase in intensity ofthe contact, and/or before or after detecting a decrease in intensity ofthe contact). A characteristic intensity of a contact is, optionallybased on one or more of: a maximum value of the intensities of thecontact, a mean value of the intensities of the contact, an averagevalue of the intensities of the contact, a top 10 percentile value ofthe intensities of the contact, a value at the half maximum of theintensities of the contact, a value at the 90 percent maximum of theintensities of the contact, or the like. In some embodiments, theduration of the contact is used in determining the characteristicintensity (e.g., when the characteristic intensity is an average of theintensity of the contact over time). In some embodiments, thecharacteristic intensity is compared to a set of one or more intensitythresholds to determine whether an operation has been performed by auser. For example, the set of one or more intensity thresholds mayinclude a first intensity threshold and a second intensity threshold. Inthis example, a contact with a characteristic intensity that does notexceed the first threshold results in a first operation, a contact witha characteristic intensity that exceeds the first intensity thresholdand does not exceed the second intensity threshold results in a secondoperation, and a contact with a characteristic intensity that exceedsthe second intensity threshold results in a third operation. In someembodiments, a comparison between the characteristic intensity and oneor more intensity thresholds is used to determine whether or not toperform one or more operations (e.g., whether to perform a respectiveoption or forgo performing the respective operation) rather than beingused to determine whether to perform a first operation or a secondoperation.

In some embodiments, a portion of a gesture is identified for purposesof determining a characteristic intensity. For example, atouch-sensitive surface may receive a continuous swipe contacttransitioning from a start location and reaching an end location (e.g.,a drag gesture), at which point the intensity of the contact increases.In this example, the characteristic intensity of the contact at the endlocation may be based on only a portion of the continuous swipe contact,and not the entire swipe contact (e.g., only the portion of the swipecontact at the end location). In some embodiments, a smoothing algorithmmay be applied to the intensities of the swipe contact prior todetermining the characteristic intensity of the contact. For example,the smoothing algorithm optionally includes one or more of: anunweighted sliding-average smoothing algorithm, a triangular smoothingalgorithm, a median filter smoothing algorithm, and/or an exponentialsmoothing algorithm. In some circumstances, these smoothing algorithmseliminate narrow spikes or dips in the intensities of the swipe contactfor purposes of determining a characteristic intensity.

The user interface figures described below optionally include variousintensity diagrams that show the current intensity of the contact on thetouch-sensitive surface relative to one or more intensity thresholds(e.g., a contact detection intensity threshold IT₀, a light pressintensity threshold IT_(L), a deep press intensity threshold IT_(D),and/or one or more other intensity thresholds). This intensity diagramis typically not part of the displayed user interface, but is providedto aid in the interpretation of the figures. In some embodiments, thelight press intensity threshold corresponds to an intensity at which thedevice will perform operations typically associated with clicking abutton of a physical mouse or a trackpad. In some embodiments, the deeppress intensity threshold corresponds to an intensity at which thedevice will perform operations that are different from operationstypically associated with clicking a button of a physical mouse or atrackpad. In some embodiments, when a contact is detected with acharacteristic intensity below the light press intensity threshold(e.g., and above a nominal contact-detection intensity threshold IT₀below which the contact is no longer detected), the device will move afocus selector in accordance with movement of the contact on thetouch-sensitive surface without performing an operation associated withthe light press intensity threshold or the deep press intensitythreshold. Generally, unless otherwise stated, these intensitythresholds are consistent between different sets of user interfacefigures.

In some embodiments, the response of the device to inputs detected bythe device depends on criteria based on the contact intensity during theinput. For example, for some “light press” inputs, the intensity of acontact exceeding a first intensity threshold during the input triggersa first response. In some embodiments, the response of the device toinputs detected by the device depends on criteria that include both thecontact intensity during the input and time-based criteria. For example,for some “deep press” inputs, the intensity of a contact exceeding asecond intensity threshold during the input, greater than the firstintensity threshold for a light press, triggers a second response onlyif a delay time has elapsed between meeting the first intensitythreshold and meeting the second intensity threshold. This delay time istypically less than 200 ms in duration (e.g., 40, 100, or 120 ms,depending on the magnitude of the second intensity threshold, with thedelay time increasing as the second intensity threshold increases). Thisdelay time helps to avoid accidental deep press inputs. As anotherexample, for some “deep press” inputs, there is a reduced-sensitivitytime period that occurs after the time at which the first intensitythreshold is met. During the reduced-sensitivity time period, the secondintensity threshold is increased. This temporary increase in the secondintensity threshold also helps to avoid accidental deep press inputs.For other deep press inputs, the response to detection of a deep pressinput does not depend on time-based criteria.

In some embodiments, one or more of the input intensity thresholdsand/or the corresponding outputs vary based on one or more factors, suchas user settings, contact motion, input timing, application running,rate at which the intensity is applied, number of concurrent inputs,user history, environmental factors (e.g., ambient noise), focusselector position, and the like. Example factors are described in U.S.patent application Ser. Nos. 14/399,606 and 14/624,296, which areincorporated by reference herein in their entireties.

An increase of characteristic intensity of the contact from an intensitybelow the light press intensity threshold IT_(L) to an intensity betweenthe light press intensity threshold IT_(L) and the deep press intensitythreshold IT_(D) is sometimes referred to as a “light press” input. Anincrease of characteristic intensity of the contact from an intensitybelow the deep press intensity threshold IT_(D) to an intensity abovethe deep press intensity threshold IT_(D) is sometimes referred to as a“deep press” input. An increase of characteristic intensity of thecontact from an intensity below the contact-detection intensitythreshold IT₀ to an intensity between the contact-detection intensitythreshold IT₀ and the light press intensity threshold IT_(L) issometimes referred to as detecting the contact on the touch-surface. Adecrease of characteristic intensity of the contact from an intensityabove the contact-detection intensity threshold IT₀ to an intensitybelow the contact-detection intensity threshold IT₀ is sometimesreferred to as detecting liftoff of the contact from the touch-surface.In some embodiments IT₀ is zero. In some embodiments, IT₀ is greaterthan zero. In some illustrations a shaded circle or oval is used torepresent intensity of a contact on the touch-sensitive surface. In someillustrations, a circle or oval without shading is used represent arespective contact on the touch-sensitive surface without specifying theintensity of the respective contact.

In some embodiments, described herein, one or more operations areperformed in response to detecting a gesture that includes a respectivepress input or in response to detecting the respective press inputperformed with a respective contact (or a plurality of contacts), wherethe respective press input is detected based at least in part ondetecting an increase in intensity of the contact (or plurality ofcontacts) above a press-input intensity threshold. In some embodiments,the respective operation is performed in response to detecting theincrease in intensity of the respective contact above the press-inputintensity threshold (e.g., the respective operation is performed on a“down stroke” of the respective press input). In some embodiments, thepress input includes an increase in intensity of the respective contactabove the press-input intensity threshold and a subsequent decrease inintensity of the contact below the press-input intensity threshold, andthe respective operation is performed in response to detecting thesubsequent decrease in intensity of the respective contact below thepress-input threshold (e.g., the respective operation is performed on an“up stroke” of the respective press input).

In some embodiments, the device employs intensity hysteresis to avoidaccidental inputs sometimes termed “jitter,” where the device defines orselects a hysteresis intensity threshold with a predefined relationshipto the press-input intensity threshold (e.g., the hysteresis intensitythreshold is X intensity units lower than the press-input intensitythreshold or the hysteresis intensity threshold is 75%, 90%, or somereasonable proportion of the press-input intensity threshold). Thus, insome embodiments, the press input includes an increase in intensity ofthe respective contact above the press-input intensity threshold and asubsequent decrease in intensity of the contact below the hysteresisintensity threshold that corresponds to the press-input intensitythreshold, and the respective operation is performed in response todetecting the subsequent decrease in intensity of the respective contactbelow the hysteresis intensity threshold (e.g., the respective operationis performed on an “up stroke” of the respective press input).Similarly, in some embodiments, the press input is detected only whenthe device detects an increase in intensity of the contact from anintensity at or below the hysteresis intensity threshold to an intensityat or above the press-input intensity threshold and, optionally, asubsequent decrease in intensity of the contact to an intensity at orbelow the hysteresis intensity, and the respective operation isperformed in response to detecting the press input (e.g., the increasein intensity of the contact or the decrease in intensity of the contact,depending on the circumstances).

For ease of explanation, the description of operations performed inresponse to a press input associated with a press-input intensitythreshold or in response to a gesture including the press input are,optionally, triggered in response to detecting: an increase in intensityof a contact above the press-input intensity threshold, an increase inintensity of a contact from an intensity below the hysteresis intensitythreshold to an intensity above the press-input intensity threshold, adecrease in intensity of the contact below the press-input intensitythreshold, or a decrease in intensity of the contact below thehysteresis intensity threshold corresponding to the press-inputintensity threshold. Additionally, in examples where an operation isdescribed as being performed in response to detecting a decrease inintensity of a contact below the press-input intensity threshold, theoperation is, optionally, performed in response to detecting a decreasein intensity of the contact below a hysteresis intensity thresholdcorresponding to, and lower than, the press-input intensity threshold.As described above, in some embodiment, the triggering of theseresponses also depends on time-based criteria being met (e.g., a delaytime has elapsed between a first intensity threshold being met and asecond intensity threshold being met).

User Interfaces and Associated Processes

Attention is now directed toward embodiments of user interfaces (“UP”)and associated processes that may be implemented on an electronicdevice, such as portable multifunction device 100 or device 300, with adisplay, a touch-sensitive surface, and one or more sensors to detectintensity of contacts with the touch-sensitive surface.

FIGS. 5A-5Z illustrate example user interfaces for interacting withhandwritten text in accordance with some embodiments. The userinterfaces in these figures are used to illustrate the processesdescribed below, including the processes in FIGS. 7A-7D. Although someof the examples which follow will be given with reference to inputs on atouch-screen display (where the touch-sensitive surface and the displayare combined), in some embodiments, the device detects inputs on atouch-sensitive surface 451 that is separate from the display 450, asshown in FIG. 4B.

FIGS. 5A-5D illustrate a sequence in which the device 100 provides auser an option to perform an operation based on characters correspondingto drawing inputs. FIGS. 5A-5B illustrate a device 100 and a stylus 502.The device 100 includes a drawing region 504 that accepts drawing inputs(e.g., a drawing input 506). In some embodiments, the drawing region 504is generated by a note-taking application (e.g., by the drawing module380 shown in FIG. 3). In some embodiments, the note-taking applicationperforms mathematical operations. In some embodiments, the note-takingapplication is a freeform spreadsheet application. In some embodiments,the device 100 detects the drawing inputs by detecting a contact of thestylus 502 with a touch-sensitive surface of the device 100. In someembodiments, in response to detecting the drawing inputs, the device 100draws strokes that correspond to characters (e.g., letters, symbolsand/or numbers). In the example of FIG. 5B, the device 100 draws strokes508 that correspond to characters 510.

Referring to FIG. 5C, in some embodiments, some subsets of charactersrepresent numerical values, words and/or phrases. In the example of FIG.5C, a first subset of characters 510 a represents a numerical value of‘$200’, a second subset of characters 510 b represents a numerical valueof ‘$300’, and a third subset of characters 510 c represents a numericalvalue of ‘$250’. In some embodiments, the device 100 receives a requestto perform an operation (e.g., mathematical operations such as addition,subtraction, multiplication, division, etc.) based on at least some ofthe characters 510 displayed in the drawing region 504. For example, thedevice 100 receives a request to perform an operation based on two ormore of the first subset of characters 510 a, the second subset ofcharacters 510 b and the third subset of characters 510 c. In someembodiments, the device 100 detects a predefined gesture 512 thatcorresponds to a request to perform an operation based on the characters510. In some embodiments, the request is to perform a mathematicaloperation based on subsets of characters that represent numericalvalues. As an example, in some embodiments, the predefined gesture 512corresponds to a request to add the numerical values represented by thefirst subset of characters 510 a, the second subset of characters 510 band the third subset of characters 510 c. In some embodiments, thedevice 100 detects the predefined gesture 512 by detecting a contactthat has a characteristic intensity, which is greater than an intensitythreshold. In such embodiments, the predefined gesture 512 is referredto as a ‘hard press’. In some embodiments, the device 100 detects thepredefined gesture 512 by detecting a contact that is associated with atime duration, which is greater than a threshold time duration. In suchembodiments, the predefined gesture 512 is referred to as a ‘longpress’. In some embodiments, the device 100 detects the predefinedgesture 512 by receiving a predefined user input (e.g., a ‘hard press’,or a ‘long press’) via a digit of a user.

Referring to FIG. 5D, in some embodiments, in response to detecting thepredefined gesture 512, the device 100 displays visual prompts inassociation with respective subsets of characters indicating that thedevice 100 can utilize the respective subsets of characters to performan operation. In the example of FIG. 5D, the device 100 displays a firstvisual prompt 520 a, a second visual prompt 520 b and a third visualprompt 520 c. The first visual prompt 520 a indicates that the device100 can perform an operation based on the first subset of characters 510a. The second visual prompt 520 b indicates that the device 100 canperform an operation based on the second subset of characters 510 b. Thethird visual prompt 520 c indicates that the device 100 can perform anoperation based on the third subset of characters 510 c. In the exampleof FIG. 5D, the visual prompts 520 a, 520 b and 520 c include dashedrectangles that encompass their corresponding subsets of characters 510a, 510 b and 510 c, respectively. In some examples, displaying thevisual prompts includes changing a display characteristic of the subsetsof characters (e.g., changing a background color of the subsets ofcharacters, for example, by highlighting the subsets of characters).Displaying the visual prompts indicates that the device 100 recognizescharacters written in handwritten text of the user, and can performoperations based on the characters written in the handwritten text.Recognizing and performing operations based on characters written inhandwritten text of the user enhances the operability of the device andmakes the user-device interface more efficient (e.g., by reducing theneed for a sequence of user inputs corresponding to typing thecharacters into the device via a keyboard) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

In some embodiments, a visual prompt includes an indication of anumerical value that the device 100 recognized based on thecorresponding subset of characters. In the example of FIG. 5D, the firstvisual prompt 520 a includes a first recognized value 522 a indicating anumerical value that the device 100 recognized from the first subset ofcharacters 510 a (e.g., ‘$200’). The second visual prompt 520 b includesa second recognized value 522 b indicating a numerical value that thedevice 100 recognized from the second subset of characters 510 b (e.g.,‘$300’). The third visual prompt 520 c includes a third recognized value522 c indicating a numerical value that the device 100 recognized fromthe third subset of characters 510 c (e.g., ‘$250’). As illustrated inFIG. 5D, in some embodiments, the device 100 displays a result field530. The result field 530 displays a resultant value for an operationbased on various subsets of characters. In other words, the resultantvalue is a function of at least some of the recognized numerical values522 a, 522 b and 522 c. Displaying the recognized numerical values 522a, 522 b and 522 c provides the user a visual confirmation that thedevice 100 has recognized the numerical values represented by thesubsets of characters 510 a, 510 b and 510 c. Providing the visualconfirmation enhances the operability of the device and makes theuser-device interface more efficient (e.g., by reducing the need for asequence of user inputs corresponding to typing the numerical valuesinto the device via a keyboard) which, additionally, reduces power usageand improves battery life of the device by enabling the user to use thedevice more quickly and efficiently.

FIGS. 5E-5L illustrate a sequence in which the device 100 receivesselections of visual prompts and computes a resultant value for theresult field 530 based on recognized values corresponding to theselected visual prompts. Referring to FIG. 5E, in some embodiments, thevisual prompts are selectable. In some embodiments, a selection of avisual prompt causes the device 100 to include the numerical valueindicated by the visual prompt into the result field 530. In the exampleof FIG. 5E, the device 100 receives a user input 540 selecting the firstvisual prompt 520 a. As illustrated in FIG. 5F, in response to receivingthe user input 540, the device 100 includes the first recognized value522 a into the result field 530. The result field 530 includes aconfirmation affordance 532 a and a cancellation affordance 532 b. Inresponse to detecting a selection of the confirmation affordance 532 a,the device 100 computes the resultant value for the result field 530based on the value(s) that are currently included in the result field530. In response to detecting a selection of the cancellation affordance532 b, the device 100 forgoes computing the resultant value for theresult field 530 and ceases display of the result field 530. Including arecognized value into the result field in response to a selection of thecorresponding visual prompt enhances the operability of the device andmakes the user-device interface more efficient (e.g., by reducing theneed for a sequence of user inputs corresponding to typing the numericalvalue into the device via a keyboard) which, additionally, reduces powerusage and improves battery life of the device by enabling the user touse the device more quickly and efficiently.

Referring to FIG. 5G, the device 100 receives a user input 542 selectingthe second visual prompt 520 b. As illustrated in FIG. 5H, in responseto receiving the user input 542, the device 100 includes the secondrecognized value 522 b into the result field 530. Referring to FIG. 5I,the device 100 receives a user input 544 selecting the third visualprompt 520 c. As illustrated in FIG. 5J, in response to receiving theuser input 544, the device 100 includes the third recognized value 522 cinto the result field 530. Referring to FIG. 5K, the device 100 receivesa user input 546 at a location corresponding to the confirmationaffordance 532 a. The user input 546 corresponds to a request to computethe resultant value for the result field 530 based on the recognizedvalues 522 a, 522 b and 522 c that are included in the result field 530.As illustrated in FIG. 5L, in response to receiving the user input 546,the device 100 computes a resultant value 534 (e.g., ‘$750’) based on afunction of the recognized values 522 a, 522 b and 522 c that were inthe result field 530 at a time the device 100 received the user input546. In the example, of FIGS. 5E-5L, the function is addition. In otherwords, in the example of FIGS. 5E-5L, the device 100 determines (e.g.,computes) the resultant value 534 by adding the recognized values 522 a,522 b and 522 c that were in the result field 530 at the time the device100 received the user input 546. More generally, in various embodiments,the device determines a resultant value in response to selections ofvisual prompts that indicate respective recognized values. Determiningthe resultant value in response to selections of visual prompts enhancesthe operability of the device and makes the user-device interface moreefficient (e.g., by reducing the need for a sequence of user inputscorresponding to typing the numerical values into the device via akeyboard) which, additionally, reduces power usage and improves batterylife of the device by enabling the user to use the device more quicklyand efficiently.

FIGS. 5M-5N illustrate a sequence in which the device 100 updates theresult field 530 in response to a drawing input that changes one of thesubsets of characters 510 a, 510 b and 510 c associated with the resultfield 530. In the example of FIG. 5M, the device 100 receives a drawinginput 548 that changes the second subset of characters 510 b. Prior toreceiving the drawing input 548, the second subset of characters 510 brepresented a numerical value of ‘$300’. However, after receiving thedrawing input 548, the second subset of characters 510 b represents anew numerical value of ‘$3000’. As illustrated in FIG. 5N, the device100 updates the result field 530 based on the change to the secondsubset of characters 510 b. For example, in FIG. 5N, the result field530 includes an updated resultant value 534′ that is a function of thenew numerical value ‘$3000’. More generally, in various embodiments, thedevice updates the result field in response to drawing inputs thatchange the subsets of characters that form the basis of the resultfield. Updating the result field in response to drawing inputs thatchange subsets of characters enhances the operability of the device andmakes the user-device interface more efficient (e.g., by reducing theneed for a sequence of user inputs corresponding to a subsequent requestto update the result field or to display a new result field based on thechanges) which, additionally, reduces power usage and improves batterylife of the device by enabling the user to use the device more quicklyand efficiently.

FIGS. 5O-5R illustrate a sequence in which the device 100 utilizes theresultant value 534 in a subsequent operation. In the example of FIG.5O, the device 100 receives a predefined gesture 550 (e.g., a ‘hardpress’ or a ‘long press’, as described herein). The predefined gesture550 corresponds to a request to perform an operation based on at leastsome of the characters 510 displayed in the drawing region 504 and/orthe resultant value 534 from a previous operation (e.g., the operationillustrated in the example of FIGS. 5K-5L). FIG. 5O includes additionalsubsets of characters (e.g., a fourth subset of characters 510 d) thatthe device 100 displayed in response to receiving additional drawinginputs.

As illustrated in FIG. 5P, in response to detecting the predefinedgesture 550, the device 100 displays visual prompts in association withrespective subsets of characters indicating that the device 100 canutilize the respective subsets of characters to perform an operation. Inthe example of FIG. 5P, the device 100 displays the first visual prompt520 a, the second visual prompt 520 b, the third visual prompt 520 c,and a fourth visual prompt 520 d. The visual prompts 520 a . . . 520 dindicate that the device 100 can perform an operation based on thesubset of characters 510 a . . . 510 d, respectively. The fourth visualprompt 520 d includes a fourth recognized value 522 d indicating anumerical value that the device 100 recognized from the fourth subset ofcharacters 510 d (e.g., ‘5’). As illustrated in FIG. 5P, the visualprompts 520 a . . . 520 d include recognized numerical values 522 a . .. 522 d, respectively. In response to the predefined gesture 550, thedevice 100 also displays the result field 530 with the resultant value534 from the previous operation. As illustrated in FIG. 5P, in responseto detecting the predefined gesture 550, the device 100 displays asecond result field 530 a for displaying a resultant value for theoperation requested by the predefined gesture 550. Displaying therecognized numerical values 522 a . . . 522 d and the result field 530indicates that the recognized numerical values 522 a . . . 522 d and theresultant value 534 in the result field 530 are available to perform anoperation requested by the predefined gesture 550. Indicating theavailability of the recognized numerical values 522 a . . . 522 d andthe resultant value for an operation requested by the predefined gesture550 enhances the operability of the device and makes the user-deviceinterface more efficient (e.g., by reducing the need for a sequence ofuser inputs corresponding to typing the recognized numerical values 522a . . . 522 d and the resultant value 534 into the device via akeyboard) which, additionally, reduces power usage and improves batterylife of the device by enabling the user to use the device more quicklyand efficiently.

In the example of FIG. 5Q, the device 100 receives a user input 552selecting the result field 530. The user input 552 corresponds to arequest to include the resultant value 534 from the previous operationinto the second result field 530 a. As such, in response to receivingthe user input 552, the device 100 includes the resultant value 534 fromthe previous operation into the second result field 530 a. Including theresultant value 534 from the previous operation into the second resultfield 530 a enhances the operability of the device and makes theuser-device interface more efficient (e.g., by reducing the need for asequence of user inputs corresponding to typing the resultant value 534,or the recognized numerical values 522 a, 522 b and 522 c from which thedevice 100 derived the resultant value 534, into the device via akeyboard) which, additionally, reduces power usage and improves batterylife of the device by enabling the user to use the device more quicklyand efficiently.

Referring to FIG. 5R, the device 100 receives a user input 554 selectingthe fourth visual prompt 520 d. The user input 554 corresponds to arequest to include the fourth recognized value 522 d into the secondresult field 530 a. In response to receiving the user input 554, thedevice 100 includes the fourth recognized value 522 d into the secondresult field 530 a. Including the fourth recognized value 522 d into thesecond result field 530 a in response to a selection of the fourthvisual prompt 520 d enhances the operability of the device and makes theuser-device interface more efficient (e.g., by reducing the need for asequence of user inputs corresponding to typing the fourth recognizednumerical value 522 d into the device via a keyboard) which,additionally, reduces power usage and improves battery life of thedevice by enabling the user to use the device more quickly andefficiently.

FIGS. 5S-5V illustrate a sequence in which the device 100 provides anoption to makes changes to the result field. In the example of FIG. 5S,the device 100 receives a user input 556 that selects the second resultfield 530 a. As illustrated in FIG. 5S, the second result field 530 aincludes a mathematical symbol (e.g., a plus sign 562 a). In someembodiments, a default operation includes addition. In such embodiments,result fields (e.g., the second result field 530 a) include the plussign 562 a by default. However, the device 100 provides the user anoption to change the default operation by selecting a differentmathematical symbol. In some embodiments, the device 100 detects theuser input 556 at a location corresponding with the mathematical symbolincluded in the second result field 530 a. In such embodiments, the userinput 556 corresponds to a request to select a different mathematicalsymbol. Referring to FIG. 5T, in response to receiving the user input556, the device 100 displays an overlay 560. In the example of FIG. 5T,the overlay 560 includes various mathematical symbols that the user canselect (e.g., the plus sign 562 a, a minus sign 562 b, a multiplicationsign 562 c and a division sign 562 d). Referring to FIG. 5U, the device100 receives a user input 558 selecting the division sign 562 d from theoverlay 560. As such, the device 100 performs a division operation withthe values in the second result field 530 a instead of the defaultaddition operation. As illustrated in FIG. 5V, the device 100 determines(e.g., computes) a second resultant value 534 a for the second resultfield 530. Displaying an overlay (e.g., the overlay 560) in response toa selection of a result field provides an intuitive and user-friendlyway to change the operation and/or the values associated with the resultfield. Providing an option to change the operation and/or the valuesassociated with the result field enhances the operability of the deviceand makes the user-device interface more efficient (e.g., by reducingthe need for a sequence of user inputs corresponding to typing differentmathematical symbols and/or values into the device via a keyboard)which, additionally, reduces power usage and improves battery life ofthe device by enabling the user to use the device more quickly andefficiently.

FIGS. 5W-5X illustrate a sequence in which the device 100 updates aresult field in response to a user input deleting characters associatedwith the result field. In the example of FIG. 5W, the device 100receives a user input 570 that corresponds to a request to delete thethird subset of characters 510 c. As shown in FIG. 5C, the third subsetof characters 510 c represented a numerical value (e.g., ‘$250’). Thenumerical value represented by the third subset of characters 510 cformed the basis for the resultant values 534 and 534 a. As such, afterthe third subset of characters 510 c is deleted, the resultant values534 and 534 a are no longer accurate. As illustrated in FIG. 5X, thedevice 100 determines an updated resultant value 534″ and an updatedsecond resultant value 534 a′ after receiving the user input 570. Asshown in FIG. 5X, the device 100 replaces the resultant values 534 and534 a with updated resultant values 534″ and 534 a′, respectively. Moregenerally, in various embodiments, the device updates the resultfield(s) in response to user inputs that change (e.g., delete) thesubsets of characters that form the basis of the result field(s).Updating the result field(s) in response to user inputs that change(e.g., delete) subsets of characters enhances the operability of thedevice and makes the user-device interface more efficient (e.g., byreducing the need for a sequence of user inputs corresponding to asubsequent request to update the result field(s) or to display a newresult field based on the change) which, additionally, reduces powerusage and improves battery life of the device by enabling the user touse the device more quickly and efficiently.

FIGS. 5Y-5Z illustrate a sequence in which the device 100 provides theuser an option to change recognized numerical values. In some scenarios,the device 100 errs at detecting numerical values. As an example, inFIG. 5Y, the device 100 displays a subset of characters 510 e thatrepresent a numerical value of ‘$280’. However, the device 100 displaysa visual prompt 520 e that includes a recognized numerical value 522 eof ‘$200’. In some embodiments, the device 100 provides an option tochange the recognized numerical values. For example, in someembodiments, the recognized numerical values include selectableaffordances that, when activated, allow the user to change therecognized numerical values that was selected. As illustrated in FIG.5Z, the device 100 receives a user input 580 selecting the recognizednumerical value 522 e. The user input 580 corresponds to a request tochange the recognized numerical value 522 e, for example, because therecognized numerical value 522 e is not accurate. In response toreceiving the user input 580, the device 100 displays a keypad 582allows the user to change the recognized numerical value 522 e. Forexample, the keypad 582 includes various affordances that correspondwith respective numbers. Providing an option to change a recognizednumerical value enhances the operability of the device and makes theuser-device interface more efficient (e.g., by reducing the need for asequence of drawing inputs corresponding to re-writing the subset ofcharacters) which, additionally, reduces power usage and improvesbattery life of the device by enabling the user to use the device morequickly and efficiently.

FIGS. 6A-6Y illustrate example user interfaces for simulatinghandwritten text in accordance with some embodiments. The userinterfaces in these figures are used to illustrate the processesdescribed below, including the processes in FIGS. 8A-8E. Although someof the examples which follow will be given with reference to inputs on atouch-screen display (where the touch-sensitive surface and the displayare combined), in some embodiments, the device detects inputs on atouch-sensitive surface 451 that is separate from the display 450, asshown in FIG. 4B.

FIGS. 6A-6B illustrate a sequence in which the device 100 displayssimulated handwritten text in response to receiving a user input thatcorresponds with a sequence of characters. FIG. 6A illustrates anote-taking interface 602 that allows a user of the device 100 to takenotes. In some embodiments, the note-taking interface 602 is generatedby the email client module 140, the instant messaging module 141, thedrawing module 380, the presentation module 382, and/or the wordprocessing module 384 shown in FIG. 3. In some embodiments, the device100 (e.g., the note-taking interface 602) receives a user inputcorresponding with a sequence of characters (e.g., a user input 604). Asillustrated in FIG. 6B, in response to receiving the user input, thedevice 100 displays the sequence of characters in simulated handwrittentext 606. In some embodiments, the simulated handwritten textcorresponds to a handwritten text of the user. For example, the device100 synthesizes the simulated handwritten text 606 based on samples ofhandwritten text of the user that the device 100 previously received. Insome embodiments, the device requests multiple samples of the samehandwritten text in order to determine natural variations in the user'shandwritten text (e.g., variations in the spacing between words andletters, variations in the amount of overlap between related characters)and use those variations to adjust the variations in the simulatedhandwritten text to more closely match the natural variations in theuser's handwritten text. As such, the simulated handwritten text 606 iswithin a degree of similarity to handwritten text of the user. Since thesimulated handwritten text 606 is within a degree of similarity tohandwritten text of the user, displaying the sequence of characters inthe simulated handwritten text 606 reduces the need for a sequence ofdrawing inputs corresponding to the sequence of characters. Displayingthe sequence of characters in simulated handwritten text enhances theoperability of the device and makes the user-device interface moreefficient (e.g., by reducing the need for drawing inputs correspondingto the user providing the sequence of characters as handwritten text)which, additionally, reduces power usage and improves battery life ofthe device by enabling the user to use the device more quickly andefficiently.

Referring to FIGS. 6C-6D, in some embodiments, the device 100 displays acharacter with a first appearance in response to a first criterion beingmet, and a second appearance in response to a second criterion beingmet. In the example of FIG. 6C, the device 100 displays the character‘w’ with a first appearance 610 a in response to the character ‘w’appearing at the beginning of a word, and a second appearance 610 b inresponse to the character ‘w’ appearing in the middle of a word. Moregenerally, in various embodiments, the device 100 displays a characterwith a first appearance in response to the character appearing at thebeginning of a word, and a second appearance in response to thecharacter appearing in the middle of a word. In some embodiments, theappearances vary based on line angle, line shape and/or line thickness.As illustrated in FIG. 6C, in the first appearance 610 a of thecharacter ‘w’, one of the outer segments of ‘w’ has a first line angle612 a (e.g., 90 degrees). By contrast, in the second appearance 610 b ofthe character ‘w’, the outer segment of ‘w’ has a second line angle 612b (e.g., an acute angle). The appearances in the simulated handwrittentext 606 are a function of variations in handwritten text of the user.For example, the device 100 varies the appearance of the character ‘w’(e.g., the line angle(s) of the character ‘w’) based on whether or notthe character ‘w’ is at the beginning of a word because the appearancesof character ‘w’ have corresponding variations in the handwritten textof the user. As such, varying the appearances of the character ‘w’results in simulated handwritten text that is within a degree ofsimilarity to the handwritten text of the user. Synthesizing handwrittentext that is within a degree of similarity to the handwritten text ofthe user enhances the operability of the device and makes theuser-device interface more efficient (e.g., by reducing the need fordrawing inputs corresponding to the user providing characters ashandwritten text) which, additionally, reduces power usage and improvesbattery life of the device by enabling the user to use the device morequickly and efficiently.

In the example of FIG. 6D, the device 100 displays the character ‘h’with a first appearance 614 a in response to the character ‘h’ appearingin the middle of a word, and a second appearance 614 b in response tothe character ‘h’ appearing at the end of a word. More generally, invarious embodiments, the device 100 displays a character with a firstappearance in response to the character appearing in the middle of aword, and a second appearance in response to the character appearing atthe end of a word. In some embodiments, the appearances vary based online angle, line shape and/or line thickness. As illustrated in FIG. 6D,in the first appearance 614 a of ‘h’, the line segments have a firstline thickness 616 a, whereas in the second appearance 614 b of ‘h’, theline segments have a second line thickness 616 b that is less than thefirst line thickness 616 a. The appearances in the simulated handwrittentext 606 are a function of variations in handwritten text of the user.For example, the device 100 varies the appearance of the character ‘h’(e.g., the line thickness of line segments that make up the character‘h’) based on whether or not the character ‘h’ is at the end of a wordbecause the appearances of the character ‘h’ have correspondingvariations in the handwritten text of the user. As such, varying theappearances of the character ‘h’ results in simulated handwritten textthat is within a degree of similarity to the handwritten text of theuser. Synthesizing handwritten text that is within a degree ofsimilarity to the handwritten text of the user enhances the operabilityof the device and makes the user-device interface more efficient (e.g.,by reducing the need for drawing inputs corresponding to the userproviding characters as handwritten text) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

Referring to FIGS. 6E-6F, in some embodiments, the device 100 varies theappearance of a set of characters (e.g., a phrase, a word, or a singleletter) to correspond to variations that inherently occur in handwrittentext of the user. In other words, the device 100 displays differentinstances of a set of characters with varying appearances becausedifferent instances of the set of characters have varying appearances inthe handwritten text of the user. In the example of FIG. 6E, the device100 displays two instances of a set of characters 618 (e.g., ‘Chatwith’). The device 100 varies the appearances of both the instances. Forexample, the device 100 displays the first instance of the set ofcharacters 618 with a first appearance 620 a, and the second instance ofthe set of characters 618 with a second appearance 620 b.

FIG. 6F illustrates expanded views of the first and second appearances620 a and 620 b of the set of characters 618. In the example of FIG. 6F,the character ‘C’ has a first appearance 622 a in the first instance ofthe set of characters 618 and a second appearance 622 b in the secondinstance of the set of characters 618. The first appearance 622 a of thecharacter ‘C’ includes a line segment 624 that is missing from thesecond appearance 622 b of the character ‘C’. Similarly, the character‘t’ has a first appearance 626 a in the first instance of the set ofcharacters 618 and a second appearance 626 b in the second instance ofthe set of characters 618. The second appearance 626 b of the character‘t’ includes a line segment 628 that is missing from the firstappearance 626 a of the character ‘t’. The character ‘h’ has a firstappearance 630 a in the first instance of the set of characters 618 anda second appearance 630 b in the second instance of the set ofcharacters 618. The first appearance 630 a of the character ‘h’ includesa line segment that has a first line angle 632 a (e.g., a right angle),whereas the second appearance 630 b of the character ‘h’ includes a linesegment that has a second line angle 632 b (e.g., an acute angle).Displaying different instances of a set of characters with varyingappearances increases the degree of similarity between the simulatedhandwritten text and the handwritten text of the user. Displayingsimulated handwritten text that is within a degree of similarity to thehandwritten text of the user enhances the operability of the device andmakes the user-device interface more efficient (e.g., by reducing theneed for drawing inputs corresponding to the user providing the set ofcharacters as handwritten text) which, additionally, reduces power usageand improves battery life of the device by enabling the user to use thedevice more quickly and efficiently.

Referring to FIGS. 6G-6H, in some embodiments, the device 100 displayssuggested strings 634 in simulated handwritten text. In someembodiments, the device 100 displays the suggested strings 634 above akeyboard 636. In some embodiments, the suggested strings 634 areselectable. In the example of FIG. 6G, the device 100 receives a userinput 638 selecting a first suggested string 634 a. As illustrated inFIG. 6H, in response to receiving the selection of the first suggestedstring 634 a, the device 100 displays the first suggested string 634 aon the display. Displaying the suggested strings 634 in simulatedhandwritten text (e.g., instead of displaying the suggested strings 634in a standard font such as ‘Arial’ or ‘Times New Roman’) provides anindication that selecting one of the suggested strings 634 causes thedevice 100 to display the selected suggested string in the simulatedhandwritten text (e.g., as opposed to the standard font). Displaying asuggested string in simulated handwritten text enhances the operabilityof the device and makes the user-device interface more efficient (e.g.,by reducing the need for drawing inputs corresponding to the suggestedstring and/or by reducing the need for a sequence of user inputscorresponding to typing the suggested string into the device via akeyboard) which, additionally, reduces power usage and improves batterylife of the device by enabling the user to use the device more quicklyand efficiently.

Referring to FIGS. 6I-6J, in some embodiments, the device 100 displays akeyboard 636 that includes characters displayed in simulated handwrittentext. In the example of FIG. 6I, the keyboard 636 includes various keysthat correspond to various characters such as ‘Q’ and/or sets ofcharacters such as ‘space’. The device 100 displays some of the keys(e.g., keys 638 a for character ‘Q’ and 638 b for character ‘T’) with afirst appearance 640 a that corresponds to simulated handwritten text,and the remaining keys (e.g., keys 638 c for character ‘U’, 638 d forcharacters ‘123’, 638 e for character ‘space’ and 638 f for characters‘return’) with a second appearance 640 b that corresponds to a standardfont (e.g., ‘Arial’, ‘Times New Roman’, etc.). In the example of FIG.6I, the device 100 has a sufficient number of handwriting samples of theuser to display some keys with the first appearance 640 a thatcorresponds to the simulated handwritten text. However, the device 100does not have a sufficient number of handwriting samples of the user todisplay all keys with the first appearance 640 a. As such, the device100 displays some keys in simulated handwritten text and the remainingkeys in the standard font. As the device 100 collects more handwritingsamples of the user, the device 100 switches the appearance of some keysfrom the standard font to the simulated handwritten text. In the exampleof FIG. 6J, the device 100 displays all keys with the first appearance640 a that corresponds to the simulated handwritten text. Displayingcharacters of the keyboard 636 in simulated handwritten text indicatesthat typing with the keyboard 636 causes the device 100 to displayselected characters in simulated handwritten text. Displaying charactersof the keyboard 636 in simulated handwritten text enhances theoperability of the device and makes the user-device interface moreefficient (e.g., by reducing the need for drawing inputs correspondingto the user providing a sequence of characters in handwritten text ofthe user) which, additionally, reduces power usage and improves batterylife of the device by enabling the user to use the device more quicklyand efficiently.

FIGS. 6K-6N illustrate a sequence in which the device 100 triggerstyping with simulated handwritten text in response to detectinginsertion of a cursor within simulated handwritten text. In the exampleof FIG. 6K, the device 100 includes a keyboard 636 that includescharacters that are displayed with the second appearance 640 bcorresponding to a standard font (e.g., ‘Arial’, ‘Times New Roman’,etc.). The device 100 receives a user input 642 that corresponds to arequest to insert a cursor 644 within simulated handwritten text 646. Asillustrated in FIG. 6L, in response to receiving the user input 642, thedevice 100 inserts the cursor 644 within the simulated handwritten text646. In response to receiving the user input 642, the device 100switches an appearance of the characters in the keyboard 636 from thesecond appearance 640 b to the first appearance 640 a corresponding tosimulated handwritten text. As such, in response to detecting that theuser input 642 inserted the cursor 644 within the simulated handwrittentext 646, the device 100 triggers typing with simulated handwrittentext. For example, as illustrated in FIGS. 6M-6N, in response toreceiving a user input 650 selecting a key for the character ‘O’, thedevice 100 displays the character ‘O’ in the simulated handwritten text.More generally, in various embodiments, in response to detecting aninsertion of a cursor within simulated handwritten text, the device 100displays a keyboard including characters that are displayed in simulatedhandwritten text that corresponds to handwritten text of the user. Inother words, in response to detecting an insertion of a cursor withinsimulated handwritten text, the device 100 triggers typing withsimulated handwritten text that corresponds to handwritten text of theuser. Triggering typing with simulated handwritten text enhances theoperability of the device and makes the user-device interface moreefficient (e.g., by reducing the need for drawing inputs correspondingto the user providing a sequence of characters in handwritten text ofthe user) which, additionally, reduces power usage and improves batterylife of the device by enabling the user to use the device more quicklyand efficiently.

Referring to FIGS. 6O-6P, the device 100 provides the user an option toenable typing with simulated handwritten text. In the example of FIG.6O, the device 100 displays a notification 652 indicating that the userhas an option to type with simulated handwritten text. In someembodiments, the device 100 displays the notification 652 when thedevice 100 has collected sufficient handwritten text samples of the userto synthesize the simulated handwritten text. In the example of FIGS.6O-6P, the device 100 collects samples of handwritten text of the user(e.g., instead of explicitly requesting specific samples of handwrittentext of the user). In the example of FIG. 6O, the device 100 receives auser input 654 that corresponds to a request to enable typing withsimulated handwritten text. As illustrated in FIG. 6P, in response toreceiving the request to enable typing with simulated handwritten text(e.g., in response to receiving the user input 654), the device 100displays a keyboard 636 including characters displayed with a firstappearance 640 a that corresponds to simulated handwritten text.Enabling typing with simulated handwritten text enhances the operabilityof the device and makes the user-device interface more efficient (e.g.,by reducing the need for drawing inputs corresponding to the userproviding a sequence of characters in handwritten text of the user)which, additionally, reduces power usage and improves battery life ofthe device by enabling the user to use the device more quickly andefficiently.

FIGS. 6Q-6R illustrate a sequence in which the device 100 explicitlyrequests specific samples of handwritten text of the user. In theexample of FIG. 6Q, the device 100 displays predefined text 656, andrequests the user to provide drawing inputs that correspond to thepredefined text 656. After displaying the predefined text 656, thedevice 100 receives drawing inputs that correspond to handwritten text658 of the user. The device 100 utilizes the handwritten text 658 of theuser to synthesize simulated handwritten text that corresponds to thehandwritten text 658 of the user. In other words, the device 100utilizes the handwritten text 658 of the user as training data for amachine-learning model that synthesizes simulated handwritten text thatis within a degree of similarity to the handwritten text 658 of theuser. In some embodiments, the device 100 requests the user to providemultiple instances of handwritten text that correspond to the predefinedtext 656. In other words, in some embodiments, the device 100 requeststhe user to handwrite the same predefined text 656 multiple times.Receiving multiple instances of handwritten text that correspond to thesame predefined text allows the device 100 to synthesize simulatedhandwritten text with varying appearances based on variations in thehandwritten text. Receiving samples of handwritten text as training dataenhances the operability of the device and makes the user-deviceinterface more efficient (e.g., by enabling the device to synthesizesimulated handwritten text based on the samples of handwritten text andreducing the need for drawing inputs corresponding to the usersubsequently providing a sequence of characters in handwritten text ofthe user) which, additionally, reduces power usage and improves batterylife of the device by enabling the user to use the device more quicklyand efficiently.

FIGS. 6S-6V illustrate a sequence in which the device 100 provides anoption to share a font that corresponds to the simulated handwrittentext. Sharing the font corresponding to the simulated handwritten textallows other users to display characters with the simulated handwrittentext. In some embodiments, the device 100 creates a new font based onthe handwritten text of the user. When the new font is selected, thedevice 100 displays characters in simulated handwritten text thatcorresponds to the handwritten text of the user. In the example of FIG.6S, the device 100 displays a sharing affordance 660 that, whenactivated, displays various sharing options. The device 100 receives auser input 662 at a location corresponding to the sharing affordance660. The user input 662 corresponds to a request to display sharingoptions. As illustrated in FIG. 6T, in response to receiving the userinput 662, the device 100 displays a share sheet 664 that includesaffordances 666 corresponding with respective sharing options. Theaffordances 666 include a share font affordance 666 a that, whenactivated, causes the device 100 to initiate transmission of a font thatgenerates simulated handwritten text corresponding to handwritten textof the user. In the example of FIG. 6U, the device 100 receives a userinput 668 at a location corresponding to the share font affordance 666a. The user input 668 corresponds to a request to share the font thatgenerates simulated handwritten text that corresponds to handwrittentext of the user. As illustrated in FIG. 6V, in response to receivingthe user input 668, the device 100 creates a new message 670 andincludes the font as an attachment 672. Sharing the font allows otherdevices associated with other users to display characters in simulatedhandwritten text that corresponds to handwritten text of the user of thedevice 100. Sharing the font enhances the operability of the device andmakes the user-device interface more efficient (e.g., by reducing theneed for drawing inputs corresponding to handwritten text andtransmitting the handwritten text to other devices associated with otherusers) which, additionally, reduces power usage and improves batterylife of the device by enabling the user to use the device more quicklyand efficiently.

FIGS. 6W-6Y illustrate a sequence in which the device 100 changes theappearance of a first character, which is displayed in simulatedhandwritten text, after receiving a request to display a secondcharacter in simulated handwritten text. The change in the appearance ofthe first character is a function of the second character. In theexample of FIG. 6W, the device 100 displays the character ‘t’ with afirst appearance 674 a. In FIG. 6X, the device 100 changes theappearance of the character ‘t’ to a second appearance 674 b afterreceiving a request to display another ‘t’. By contrast, in FIG. 6Y, thedevice 100 changes the appearance of the character ‘t’ to a thirdappearance 674 c after receiving a request to display the character ‘h’.As illustrated in the example of FIGS. 6W-6Y, the device 100 changes theappearance of the character ‘t’ based on which character appears afterthe character ‘t’. In some embodiments, after receiving a request todisplay a character, the device 100 varies the appearance of one or moreprevious characters to correspond to similar variations in thehandwritten text of the user. Varying the appearance of previouscharacters based on subsequent characters increases a degree ofsimilarity between the simulated handwritten text and the handwrittentext of the user. Varying the appearance of previous character based ona function of subsequent characters enhances the operability of thedevice and makes the user-device interface more efficient (e.g., byreducing the need for drawing inputs corresponding to the user providinga sequence of characters in handwritten text of the user) which,additionally, reduces power usage and improves battery life of thedevice by enabling the user to use the device more quickly andefficiently.

FIGS. 7A-7D illustrate a flow diagram of a method 700 of interactingwith handwritten text in accordance with some embodiments. The method700 is performed at an electronic device (e.g., the device 100 in FIG.1A, or the device 300 in FIG. 3) with one or more processors,non-transitory memory, a display, and one or more input devices. In someembodiments, the display is a touch-screen display and the one or moreinput devices are on or integrated with the display. In someembodiments, the display is separate from the one or more input devices.Some operations in method 700 are, optionally, combined and/or the orderof some operations is, optionally, changed.

Referring to FIG. 7A, at a device including a touch-sensitive display,the device displays (702), on the touch-sensitive display, a drawingregion (e.g., the drawing region 504 shown in FIG. 5A). Whiledisplaying, the drawing region, the device detects (702) a sequence ofdrawing inputs on the touch-sensitive display (e.g., the drawing input506 shown in FIG. 5A). In some embodiments, the drawing region isgenerated by a note-taking application. In some embodiments, thenote-taking application performs mathematical operations. In someexamples, the note-taking application is a freeform spreadsheetapplication.

In response to detecting the sequence of drawing inputs, the devicedraws (706) (e.g., displays and/or renders) a plurality of strokes inthe drawing region. The plurality of strokes correspond to a pluralityof characters. In some implementations, at least some of the charactersinclude numerical values. As an example, in FIG. 5B, the device 100draws strokes 508 that correspond to characters 510.

After detecting the sequence of drawing inputs on the touch-sensitivedisplay, the device detects (706), on the touch-sensitive display, apredefined gesture that corresponds to a request to perform an operationbased on the plurality of characters represented by the plurality ofstrokes. In some embodiments, the predefined gesture includes a hardpress or a long press, as described herein. As an example, in FIG. 5C,the device 100 detects the predefined gesture 512 that corresponds to arequest to perform an operation based on the characters 510.

In response to detecting the predefined gesture, the device concurrentlydisplays (708), on the touch-sensitive display, a first visual promptindicating that a first subset of one or more characters in theplurality of characters can be used to perform the operation and asecond visual prompt indicating that a second subset of one or morecharacters in the plurality of characters can be used to perform theoperation. As an example, in FIG. 5D, the device 100 displays the firstvisual prompt 520 a indicating that the device 100 can perform anoperation based on the first subset of characters 510 a, and the secondvisual prompt 520 b indicating that the device 100 can perform anoperation based on the second subset of characters 510 b. Displaying thevisual prompts indicates that the device recognizes characters writtenin handwritten text of the user, and can perform operations based on thecharacters written in the handwritten text. Recognizing and performingoperations based on characters written in handwritten text of the userenhances the operability of the device and makes the user-deviceinterface more efficient (e.g., by reducing the need for a sequence ofuser inputs corresponding to typing the characters into the device via akeyboard) which, additionally, reduces power usage and improves batterylife of the device by enabling the user to use the device more quicklyand efficiently.

In some embodiments, the detecting the sequence of drawing inputsincludes (704) receiving the sequence of drawing inputs via a stylus(e.g., via the stylus 502 shown in FIG. 5A), and detecting a predefinedgesture includes receiving the predefined gesture via a digit of a user(e.g., receiving the predefined gesture 512 shown in FIG. 5C).

Referring to FIG. 7B, in some embodiments, the device displays (710), onthe touch-sensitive display, a result field that includes a resultantvalue for the operation. The resultant value is a function of the firstsubset of one or more characters and the second subset of one or morecharacters. In some embodiments, the device detects (712) the predefinedgesture at a particular location and displays (712) the result field atthe particular location. As an example, in FIG. 5D, the device 100displays the result field 530 at a location corresponding to thepredefined gesture 512. As illustrated in FIG. 5L, the result field 530includes a resultant value 534 for the operation. Displaying the resultfield with the resultant value enhances the operability of the deviceand makes the user-device interface more efficient (e.g., by reducingthe need for a sequence of user inputs corresponding to typing theresultant value into the device via a keyboard) which, additionally,reduces power usage and improves battery life of the device by enablingthe user to use the device more quickly and efficiently.

In some embodiments, the device renders (714) the resultant value in asimulated handwritten text that is within a degree of similarity to theplurality of strokes displayed in the drawing region. In someembodiments, an appearance of the simulated handwritten text correspondsto an appearance of handwritten text of the respective user. In someembodiments, the simulated handwritten text is generated by one or moreof the steps of method 800 described in greater detail below. Displayingthe resultant value in the simulated handwritten text enhances theoperability of the device and makes the user-device interface moreefficient (e.g., by reducing the need for a sequence of user inputscorresponding to typing the resultant value into the device via akeyboard) which, additionally, reduces power usage and improves batterylife of the device by enabling the user to use the device more quicklyand efficiently.

In some embodiments, the first subset of one or more characters and thesecond subset of one or more characters are associated with (716) one ormore of a symbol (e.g., a ‘$’ sign) and a unit of measurement (e.g.,‘kg’, ‘m’, etc.). The result field further includes one or more of thesymbol and the unit of measurement. As an example, in FIG. 5L, theresult field 530 includes the ‘$’ sign, for example, because the subsetsof characters 510 a, 510 b and 510 c include the ‘$’ sign. Including thesymbol and/or the unit of measurement associated with the subsets ofcharacters into the result field indicates that the resultant value inthe result field is a function of the subsets of characters. Includingthe symbol and/or unit of measurement in the result field enhances theoperability of the device and makes the user-device interface moreefficient (e.g., by reducing the need for a sequence of user inputscorresponding to typing the resultant value into the device via akeyboard) which, additionally, reduces power usage and improves batterylife of the device by enabling the user to use the device more quicklyand efficiently.

In some embodiments, the first subset of one or more characters isassociated with (718) a first unit of measurement (e.g., ‘lb’) and thesecond subset of one or more characters is associated with (718) asecond unit of measurement (e.g., ‘kg’) that is different from the firstunit of measurement. In such embodiments, displaying the result fieldincludes (718) converting the first subset of one or more charactersfrom the first unit of measurement into the second unit of measurement(e.g., convert the first subset of characters from ‘lb’ to ‘kg’). Thedevice determines (718) the resultant value based on a function of theconverted first subset of one or more characters and the second subsetof one or more characters (e.g., add two values that are both in ‘kg’).Performing unit conversions enhances the operability of the device andmakes the user-device interface more efficient (e.g., by reducing theneed for a sequence of user inputs corresponding to typing thecharacters in accordance with the converted unit of measurement) which,additionally, reduces power usage and improves battery life of thedevice by enabling the user to use the device more quickly andefficiently.

In some embodiments, the device receives (720) a request to perform asubsequent operation and performs (720) the subsequent operation basedon a function of the resultant value. As an example, in FIGS. 5O-5R, thedevice 100 utilizes the resultant value 534 in a subsequent operation.For example, as shown in FIG. 5V, the second result field 530 acorresponding to a second operation is based on the resultant value 534from a previous operation. Performing the subsequent operation based ona function of the resultant value enhances the operability of the deviceand makes the user-device interface more efficient (e.g., by reducingthe need for a sequence of user inputs corresponding to typing theresultant value into the device via a keyboard) which, additionally,reduces power usage and improves battery life of the device by enablingthe user to use the device more quickly and efficiently.

Referring to FIG. 7C, in some embodiments, the device detects (722) auser selection of the result field. In response to receiving the userselection of the result field (e.g., tapping and holding the resultfield), the device displays (722) an overlay that includes one or moremathematical symbols that are associated with the operation, a firstnumerical value that corresponds with the first subset of one or morecharacters, and a second numerical value that corresponds with thesecond subset of one or more characters. In some embodiments, the devicereceives (724) a user input changing one or more of the one or moremathematical symbols, the first numerical value, and the secondnumerical value. In some implementations, the user can change thesymbols/values by writing over them. In some implementations, the usercan erase an existing symbol/value. In some implementations, the usercan write an additional symbol/value. In response to the user input, thedevice updates (724) the resultant value based on the changes to the oneor more of the one or more mathematical symbols, the first numericalvalue and the second numerical value. As an example, in FIGS. 5S-5V, thedevice 100 displays an overlay 560 that provides an option to makechanges to the operation. Displaying an overlay (e.g., the overlay 560)in response to a selection of a result field provides an intuitive anduser-friendly way to change the operation and/or the values associatedwith the result field. Providing an option to change the operationand/or the values associated with the result field enhances theoperability of the device and makes the user-device interface moreefficient (e.g., by reducing the need for a sequence of user inputscorresponding to typing different mathematical symbols and/or valuesinto the device via a keyboard) which, additionally, reduces power usageand improves battery life of the device by enabling the user to use thedevice more quickly and efficiently.

In some embodiments, the device detects (726), via a microphone, a voiceinput that indicates the operation. For example, in some embodiments,the device receives a spoken command (e.g., “sum all the numbers”) toperform an operation.

Referring to FIG. 7D, in some embodiments, the operation includes (728)a formula. In some implementations, the formula is a default formulathat can be changed by the user. For example, in some implementations,the default formula is addition. The first visual prompt indicates (728)that the first subset of one or more characters represents a firstnumerical value that can be included in the formula and the secondvisual prompt indicates (728) that the second subset of one or morecharacters represents a second numerical value that can be included inthe formula. As an example, in FIGS. 5S-5V, the device 100 displays anoverlay 560 that provides an option to change the default formula.Providing an option to change the default formula enhances theoperability of the device and makes the user-device interface moreefficient (e.g., by reducing the need for a sequence of user inputscorresponding to typing different mathematical symbols correspondingwith a different formula) which, additionally, reduces power usage andimproves battery life of the device by enabling the user to use thedevice more quickly and efficiently.

In some embodiments, the device receives (730) a user input selectingthe first visual prompt. In some implementations, the user taps on thefirst visual prompt to select the first visual prompt. In response tothe user input selecting the first visual prompt, the device includes(730) the first numerical value in the formula. The device receives(730) a user input selecting the second visual prompt. In response tothe user input selecting the second visual prompt, the device includes(730) the second numerical value in the formula. As an example, in FIGS.5E-5F, the device 100 includes the first recognized numerical value 522a into the result field 530 in response to receiving the user input 540selecting the first visual prompt 520 a. Including a recognized valueinto the result field in response to a selection of the correspondingvisual prompt enhances the operability of the device and makes theuser-device interface more efficient (e.g., by reducing the need for asequence of user inputs corresponding to typing the numerical value intothe device via a keyboard) which, additionally, reduces power usage andimproves battery life of the device by enabling the user to use thedevice more quickly and efficiently.

In some embodiments, the first affordance for changing the firstnumerical value includes (732) the first numerical value. The secondaffordance for changing the second numerical value includes (732) thesecond numerical value. In some embodiments, the first visual promptincludes (734) a first affordance for changing the first numericalvalue. The second visual prompt includes (734) a second affordance forchanging the second numerical value. As an example, in FIGS. 5Y-5Z, thedevice 100 receives a user input 580 corresponding to a request tochange the recognized numerical value 522 e. In response to receivingthe user input 580, the device 100 displays a keypad 582 that allows theuser to change the recognized numerical value 522 e. Providing an optionto change a numerical value enhances the operability of the device andmakes the user-device interface more efficient (e.g., by reducing theneed for a sequence of drawing inputs corresponding to re-writing thesubset of characters) which, additionally, reduces power usage andimproves battery life of the device by enabling the user to use thedevice more quickly and efficiently.

In some embodiments, in response to a user input changing one or more ofthe first numerical value and the second numerical value, the deviceupdates (736) the formula based on a change to one or more of the firstnumerical value and the second numerical value. As an example, in FIGS.5M-5N, the device 100 receives a drawing input 548 that changes thesecond subset of characters 510 b. In response to receiving the drawinginput 548, the device 100 determines and displays the updated resultantvalue 534′ based on the change to the second subset of characters 510 b.Updating the result field in response to drawing inputs that changesubsets of characters enhances the operability of the device and makesthe user-device interface more efficient (e.g., by reducing the need fora sequence of user inputs corresponding to a subsequent request toupdate the result field or to display a new result field based on thechanges) which, additionally, reduces power usage and improves batterylife of the device by enabling the user to use the device more quicklyand efficiently.

It should be understood that the particular order in which theoperations in FIGS. 7A-7D have been described is merely exemplary and isnot intended to indicate that the described order is the only order inwhich the operations could be performed. One of ordinary skill in theart would recognize various ways to reorder the operations describedherein. Additionally, it should be noted that details of other processesdescribed herein with respect to other methods described herein (e.g.,method 800) are also applicable in an analogous manner to method 700described above with respect to FIGS. 7A-7D. For example, the userinterfaces, user interface elements, drawing inputs, predefinedgestures, visual prompts, etc., described above with reference to method700 optionally have one or more of the characteristics of the userinterfaces, user interface elements, drawing inputs, predefinedgestures, visual prompts, etc. described herein with reference to othermethods described herein (e.g., method 800). For brevity, these detailsare not repeated here.

The operations in the information processing methods described aboveare, optionally implemented by running one or more functional modules ininformation processing apparatus such as general purpose processors(e.g., as described above with respect to FIGS. 1A and 3) or applicationspecific chips. Further, the operations described above with referenceto FIGS. 7A-7D are, optionally, implemented by components depicted inFIGS. 1A-1B, or FIG. 3. For example, the detect operation 706 is,optionally, implemented by event sorter 170, event recognizer 180, andevent handler 190. Event monitor 171 in event sorter 170 detects acontact on touch-sensitive display 112, and event dispatcher module 174delivers the event information to application 136-1. A respective eventrecognizer 180 of application 136-1 compares the event information torespective event definitions 186, and determines whether a first contactat a first location on the touch-sensitive surface (or whether rotationof the device) corresponds to a predefined event or sub-event, such asselection of an object on a user interface, or rotation of the devicefrom one orientation to another. When a respective predefined event orsub-event is detected, event recognizer 180 activates an event handler190 associated with the detection of the event or sub-event. Eventhandler 190 optionally uses or calls data updater 176 or object updater177 to update the application internal state 192. In some embodiments,event handler 190 accesses a respective GUI updater 178 to update whatis displayed by the application. Similarly, it would be clear to aperson having ordinary skill in the art how other processes can beimplemented based on the components depicted in FIGS. 1A-1B.

FIGS. 8A-8E illustrate a flow diagram of a method 800 of displayingcharacters in simulated handwritten text that corresponds to handwrittentext of a user. The method 800 is performed at an electronic device(e.g., the device 100 in FIG. 1A, or the device 300 in FIG. 3) with aone or more processors, non-transitory memory, a display, and one ormore input devices. In some embodiments, the display is a touch-screendisplay and the one or more input devices are on or integrated with thedisplay. In some embodiments, the display is separate from the one ormore input devices. Some operations in method 800 are, optionally,combined and/or the order of some operations is, optionally, changed.

Referring to FIG. 8A, at a device including a display and one or moreinput devices, the device receives (802), via the one or more inputdevices, a user input that corresponds with a sequence of characters. Asan example, in FIG. 6A, the device 100 receives the user input 604 thatcorresponds to a request to type the character ‘T’. In response toreceiving the user input, the device displays (804), on the display,simulated handwritten text that includes varying the appearance ofcharacters in the simulated handwritten text based on variations thatwere detected in handwritten text of a respective user. As an example,in FIG. 6B, the device 100 displays the simulated handwritten text 606.In some embodiments, the simulated handwritten text is within a degreeof similarity to handwritten text of the user. Since the simulatedhandwritten text is within a degree of similarity to handwritten text ofthe user, displaying the sequence of characters in the simulatedhandwritten text reduces the need for a sequence of drawing inputscorresponding to the sequence of characters. Displaying the sequence ofcharacters in simulated handwritten text enhances the operability of thedevice and makes the user-device interface more efficient (e.g., byreducing the need for drawing inputs corresponding to the user providingthe sequence of characters as handwritten text) which, additionally,reduces power usage and improves battery life of the device by enablingthe user to use the device more quickly and efficiently.

Displaying the simulated handwritten text includes (806), in accordancewith a determination that a first criterion is met, a first character inthe sequence of characters has a first appearance that corresponds tothe appearance of the first character in handwritten text of therespective user. In some embodiments, in response to receiving the userinput that corresponds with the sequence of characters and in accordancewith a determination that a second criterion is met, the first characterin the sequence of characters (808) has a second appearance thatcorresponds to the appearance of the first character in handwritten textof the respective user, wherein the second appearance of the firstcharacter is different than the first appearance of the first character.As an example, in FIG. 6C, the device 100 displays the character ‘w’with a first appearance 610 a in response to the character ‘w’ appearingat the beginning of a word, and a second appearance 610 b in response tothe character ‘w’ appearing in the middle of a word. Varying theappearances of the first character results in simulated handwritten textthat is within a degree of similarity to the handwritten text of theuser. Synthesizing handwritten text that is within a degree ofsimilarity to the handwritten text of the user enhances the operabilityof the device and makes the user-device interface more efficient (e.g.,by reducing the need for drawing inputs corresponding to the userproviding characters as handwritten text) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

Referring to FIG. 8B, in some embodiments, the device detects (810) theuser input via the microphone (e.g., the device 100 detects that theuser of the device 100 is dictating the sequence of characters). In someembodiments, the device receives (812) the user input via one or more ofa messaging application and a notes application. In some embodiments,the user is typing a message in the messaging application, and themessage appears in the simulated handwritten text as the user is typingthe message. In some embodiments, the user is taking notes in the notesapplication, and the notes appear in the simulated handwritten text asthe user is typing the notes. In some embodiments, receiving the userinput includes (814) receives a request to retrieve an electronic file(e.g., a text file with typed text). In some examples, the electronicfile is saved on the device. In some examples, the electronic file isstored remotely.

In some embodiments, the device, prior to receiving the user input thatcorresponds with the sequence of characters, receives (816) thehandwritten text of the respective user. In some embodiments, thedevice, during an enrollment for displaying the simulated handwrittentext, displays (818) a predefined text string (e.g., the predefined text656 shown in FIGS. 6Q-6R). In response to displaying the predefined textstring, the device receives (818) the handwritten text, where thehandwritten text corresponds with the predefined text string. As anexample, in FIGS. 6Q-6R, the device 100 receives samples of handwrittentext 658 that correspond to predefined text 656 (e.g., as part of atraining program). In some embodiments, the device utilizes thehandwritten text as training data for a machine-learning model thatsynthesizes simulated handwritten text. Receiving samples of handwrittentext as training data enhances the operability of the device and makesthe user-device interface more efficient (e.g., by enabling the deviceto synthesize simulated handwritten text based on the samples ofhandwritten text and reducing the need for drawing inputs correspondingto the user subsequently providing a sequence of characters inhandwritten text of the user) which, additionally, reduces power usageand improves battery life of the device by enabling the user to use thedevice more quickly and efficiently.

In some embodiments, the handwritten text is received (820) outside anenrollment for displaying the simulated handwritten text (e.g., thedevice does not explicitly request the handwritten text, rather thedevice passively gathers the handwritten text). In some embodiments, thedevice, in response to a determination that an amount of receivedhandwritten text is greater than a threshold amount, presents (822) anotification indicating that the device has received a sufficient amountof handwritten text to generate the simulated handwritten text. In someembodiments, the notification includes an affordance that, whenactivated, enrolls the user for displaying simulated handwritten text.As an example, in FIGS. 6O-6P, the device 100 displays the notification652 and receives a user input 654 corresponding to a request to enabletyping with simulated handwritten text. Displaying the notificationprovides the user an option to enable typing with simulated handwrittentext. Enabling typing with simulated handwritten text enhances theoperability of the device and makes the user-device interface moreefficient (e.g., by reducing the need for drawing inputs correspondingto the user providing a sequence of characters in handwritten text ofthe user) which, additionally, reduces power usage and improves batterylife of the device by enabling the user to use the device more quicklyand efficiently.

In some embodiments, the device detects (824) an input corresponding toa request to insert a cursor. In some embodiments, the device determineswhether or not the cursor is inserted within the simulated handwrittentext. In response to detecting the input that corresponds to the requestto insert the cursor and in accordance with a determination that thecursor is inserted within the simulated handwritten text, the devicedisplays (824) a keyboard including characters that correspond withhandwritten text of the respective user. In some implementations, thecharacters on the keyboard appear as handwritten characters. In responseto detecting the input that corresponds to the request to insert thecursor and in accordance with a determination that the cursor is notinserted within the simulated handwritten text, the device displays(824) the keyboard including characters that correspond with apredetermined font (e.g., the characters on the keyboard are displayedin a standard font). As an example, in FIGS. 6K-6N, the device 100detects insertion of the cursor 644 within the simulated handwrittentext 646. In response to detecting the insertion of the cursor 644within the simulated handwritten text 646, the device 100 switches anappearance of the characters in the keyboard 636 from the secondappearance 640 b to the first appearance 640 a corresponding tosimulated handwritten text. Displaying characters of the keyboard insimulated handwritten text triggers typing with the simulatedhandwritten text. Triggering typing with simulated handwritten textenhances the operability of the device and makes the user-deviceinterface more efficient (e.g., by reducing the need for drawing inputscorresponding to the user providing a sequence of characters inhandwritten text of the user) which, additionally, reduces power usageand improves battery life of the device by enabling the user to use thedevice more quickly and efficiently.

Referring to FIG. 8C, in some embodiments, the device synthesizes (826)a font based on the handwritten text of the respective user and shares(826) the font with another user (e.g., with another device associatedwith the other user). The other user can use the font to display textwith one of the first appearance and the second appearance. In someimplementations, the font can be shared via a message. In someimplementations, the other user can configure their device to displaymessages received from the first user in the font that corresponds withthe first user's handwriting. As an example, in FIGS. 6S-6V, the device100 provides an option to share a font that corresponds to the simulatedhandwritten text. For example, in response to receiving the user input668, the device 100 creates a new message 670 and includes the font asan attachment 672. Sharing the font allows other devices associated withother users to display characters in simulated handwritten text thatcorresponds to handwritten text of the user of the device 100. Sharingthe font enhances the operability of the device and makes theuser-device interface more efficient (e.g., by reducing the need fordrawing inputs corresponding to handwritten text and transmitting thehandwritten text to other devices associated with other users) which,additionally, reduces power usage and improves battery life of thedevice by enabling the user to use the device more quickly andefficiently.

In some embodiments, the device, in accordance with a determination thata second character in the sequence of characters does not correspondwith handwritten text of the respective user, displays (828) the secondcharacter in a predefined font. As an example, in FIG. 6I, the device100 displays some of the keys (e.g., keys 638 a and 638 b) with a firstappearance 640 a that corresponds to simulated handwritten text, and theremaining keys (e.g., keys 638 c, 638 d, 638 e and 638 f) with a secondappearance 640 b that corresponds to a standard font (e.g., ‘Arial’,‘Times New Roman’, etc.). Displaying the second character in thepredefined font indicates that the device does not have sufficienthandwritten samples of the second character to synthesize simulatedhandwritten text for the second character.

In some embodiments, the device, in accordance with a determination thata second character in the sequence of characters does not correspondwith handwritten text of the respective user, synthesizes (830) thesecond character based on sub-character features of other charactersthat correspond with handwritten text of the respective user. In someimplementations, the second character is a symbol (e.g., a Chinesecharacter) with no corresponding handwritten text of the user. In someembodiments, the device synthesizes the second character by selectingsub-character features (e.g., line segments, line angles, linethicknesses, etc.) of other character that are within a degree ofsimilarity of the second character. Synthesizing the second characterbased on sub-character features of other characters enables the deviceto display the second character in simulated handwritten text.Displaying the second character in simulated handwritten text enhancesthe operability of the device and makes the user-device interface moreefficient (e.g., by reducing the need for drawing inputs correspondingto the second character) which, additionally, reduces power usage andimproves battery life of the device by enabling the user to use thedevice more quickly and efficiently.

In some embodiments, the device displays (832) the simulated handwrittentext as suggested text (e.g., in a notes application, in a messagingapplication, etc.). As an example, in FIGS. 6G-6H, the device 100displays suggested strings 634 above a keyboard 636. Displaying asuggested string in simulated handwritten text enhances the operabilityof the device and makes the user-device interface more efficient (e.g.,by reducing the need for drawing inputs corresponding to the suggestedstring and/or by reducing the need for a sequence of user inputscorresponding to typing the suggested string into the device via akeyboard) which, additionally, reduces power usage and improves batterylife of the device by enabling the user to use the device more quicklyand efficiently.

In some embodiments, the device detects (834) an input corresponding toa request to insert a cursor. The device receives (834), via the one ormore input devices, a second user input that corresponds with a secondsequence of characters. In some embodiments, after detecting the inputcorresponding to the request to insert the cursor, the device determines(834) whether or not the cursor is inserted within the simulatedhandwritten text. In response to receiving the second user input and inaccordance with a determination that the cursor is inserted within thesimulated handwritten text, the device displays (834) the secondsequence of characters in simulated handwritten text that correspondswith handwritten text of the respective user. In response to receivingthe second user input and in accordance with a determination that thecursor is not inserted within the simulated handwritten text, the devicedisplays (834) the second sequence of characters in a predeterminedfont. As an example, in FIGS. 6K-6N, the device 100 detects theinsertion of the cursor 644 within the simulated handwritten text 646.In response to detecting the insertion of the cursor 644 within thesimulated handwritten text 646, the device 100 switches an appearance ofthe characters in the keyboard 636 from the second appearance 640 b tothe first appearance 640 a corresponding to simulated handwritten text.In other words, in response to detecting an insertion of a cursor withinsimulated handwritten text, the device 100 triggers typing withsimulated handwritten text that corresponds to handwritten text of theuser. Triggering typing with simulated handwritten text enhances theoperability of the device and makes the user-device interface moreefficient (e.g., by reducing the need for drawing inputs correspondingto the user providing a sequence of characters in handwritten text ofthe user) which, additionally, reduces power usage and improves batterylife of the device by enabling the user to use the device more quicklyand efficiently.

Referring to FIG. 8D, in some embodiments, the first appearance isassociated with (836) one or more of a first line angle, a first lineshape and a first line thickness. The second appearance is associated(836) with one or more of a second line angle that is different from thefirst line angle, a second line shape that is different from the firstline shape and a second line thickness that is different from the firstline thickness. In some embodiments, the first character includes (838)a first stroke and a second stroke. The first appearance is associatedwith (838) a first proportion between the first stroke and the secondstroke. The second appearance is associated with (838) a secondproportion between the first stroke and the second stroke, the secondproportion being different from the first proportion. As an example, inFIG. 6C, in the first appearance 610 a of the character ‘w’, one of theouter segments of ‘w’ has a first line angle 612 a (e.g., 90 degrees).By contrast, in the second appearance 610 b of the character ‘w’, theouter segment of ‘w’ has a second line angle 612 b (e.g., an acuteangle). Varying the appearances of a character results in simulatedhandwritten text that is within a degree of similarity to thehandwritten text of the user. Synthesizing handwritten text that iswithin a degree of similarity to the handwritten text of the userenhances the operability of the device and makes the user-deviceinterface more efficient (e.g., by reducing the need for drawing inputscorresponding to the user providing characters as handwritten text)which, additionally, reduces power usage and improves battery life ofthe device by enabling the user to use the device more quickly andefficiently.

In some embodiments, the variation between the first appearance and thesecond appearance is (840) a function of a variation in the handwrittentext of the respective user. In some implementations, the variation inthe appearances is directly proportion to the variation in thehandwritten text of the user. For example, the greater the variation inthe handwritten text of the user, the greater the variation in theappearances. In some embodiments, the device determines (842) whetherone of the first criterion and the second criterion are met based on arandomizing function. In some implementations, the randomizing functionis based on a random seed that is used to initialize a pseudorandomnumber generator. In some implementations, the first criterion is met ifthe output of the pseudorandom number generator is greater than athreshold number and the second criterion is met if the output of thepseudorandom number generator is not greater than the threshold number.As an example, in FIGS. 6E-6F, the device 100 displays the set ofcharacters 618 with the first appearance 620 a in response to the outputof the pseudorandom number generator being greater than the thresholdnumber, and the device 100 displays the set of characters 618 with thesecond appearance 620 b in response to the output of the pseudorandomnumber generator being less than the threshold number. Varying theappearances increases the degree of similarity between the simulatedhandwritten text and the handwritten text of the user. Varying theappearances enhances the operability of the device and makes theuser-device interface more efficient (e.g., by reducing the need fordrawing inputs corresponding to the user providing characters ashandwritten text) which, additionally, reduces power usage and improvesbattery life of the device by enabling the user to use the device morequickly and efficiently.

In some embodiments, the device determines (844) that the firstcriterion is met when the first character is between a second characterand a third character (e.g., the first criterion applies to letters thatare situated between other letters). The device determines (844) thatthe second criterion is met when the first character is adjacent thesecond character and not adjacent the third character (e.g., the secondcriterion applies to letters that are on the fringes, for example, tofirst and last letters of words). As an example, in FIG. 6C, in thefirst instance of the character ‘w’, the character ‘w’ is situated atthe beginning of a word. In the example of FIG. 6C, in the secondinstance of the character ‘w’, the character ‘w’ is situated in themiddle of a word. Varying the appearances of a character results insimulated handwritten text that is within a degree of similarity to thehandwritten text of the user. Synthesizing handwritten text that iswithin a degree of similarity to the handwritten text of the userenhances the operability of the device and makes the user-deviceinterface more efficient (e.g., by reducing the need for drawing inputscorresponding to the user providing characters as handwritten text)which, additionally, reduces power usage and improves battery life ofthe device by enabling the user to use the device more quickly andefficiently.

Referring to FIG. 8E, in some embodiments, the device, after displayingthe first character in accordance with one of the first appearance andthe second appearance, receives (846) a second character in the sequenceof characters. In response to receiving the second character in thesequence of characters and in accordance with a determination that athird criterion is met, the device changes (846) the display of thefirst character from one of the first appearance and the secondappearance to a third appearance that corresponds to the appearance ofthe first character in handwritten text of the respective user. In someimplementations, the third criterion specifies that the second characteris from a predefined set of characters. For example, as illustrated inFIGS. 6W-6Y, the appearance of the character ‘t’ changes to a thirdappearance 674 c after receiving the character ‘h’. In someimplementations, the third criterion specifies that the second characteris a punctuation. In response to receiving the second character in thesequence of characters and in accordance with a determination that afourth criterion is met, the device changes (846) the display of thefirst character from one of the first appearance and the secondappearance to a fourth appearance that corresponds to the appearance ofthe first character in handwritten text of the respective user. Thefourth appearance of the first character is different than the thirdappearance of the first character. In some implementations, the fourthcriterion specifies that the second character is not from the predefinedset of characters. For example, as illustrated in FIGS. 6W-6Y, theappearance of character ‘t’ changes to a second appearance 674 b afterthe device 100 another instance of the character ‘t’. In someimplementations, the fourth criterion specifies that the secondcharacter is not a punctuation. Varying the appearance of previouscharacters based on a function of subsequent characters enhances theoperability of the device and makes the user-device interface moreefficient (e.g., by reducing the need for drawing inputs correspondingto the user providing a sequence of characters in handwritten text ofthe user) which, additionally, reduces power usage and improves batterylife of the device by enabling the user to use the device more quicklyand efficiently.

It should be understood that the particular order in which theoperations in FIGS. 8A-8E have been described is merely exemplary and isnot intended to indicate that the described order is the only order inwhich the operations could be performed. One of ordinary skill in theart would recognize various ways to reorder the operations describedherein. Additionally, it should be noted that details of other processesdescribed herein with respect to other methods described herein (e.g.,method 700) are also applicable in an analogous manner to method 800described above with respect to FIGS. 8A-8E. For example, the userinterfaces, user interface elements, simulated handwritten text, firstcriterion, second criterion, etc., described above with reference tomethod 800 optionally have one or more of the characteristics of theuser interfaces, user interface elements, simulated handwritten text,first criterion, second criterion, etc. described herein with referenceto other methods described herein (e.g., method 700). For brevity, thesedetails are not repeated here.

The operations in the information processing methods described aboveare, optionally implemented by running one or more functional modules ininformation processing apparatus such as general purpose processors(e.g., as described above with respect to FIGS. 1A and 3) or applicationspecific chips. Further, the operations described above with referenceto FIGS. 8A-8E are, optionally, implemented by components depicted inFIGS. 1A-1B, or FIG. 3. For example, the receive operation 802 is,optionally, implemented by event sorter 170, event recognizer 180, andevent handler 190. Event monitor 171 in event sorter 170 detects acontact on touch-sensitive display 112, and event dispatcher module 174delivers the event information to application 136-1. A respective eventrecognizer 180 of application 136-1 compares the event information torespective event definitions 186, and determines whether a first contactat a first location on the touch-sensitive surface (or whether rotationof the device) corresponds to a predefined event or sub-event, such asselection of an object on a user interface, or rotation of the devicefrom one orientation to another. When a respective predefined event orsub-event is detected, event recognizer 180 activates an event handler190 associated with the detection of the event or sub-event. Eventhandler 190 optionally uses or calls data updater 176 or object updater177 to update the application internal state 192. In some embodiments,event handler 190 accesses a respective GUI updater 178 to update whatis displayed by the application. Similarly, it would be clear to aperson having ordinary skill in the art how other processes can beimplemented based on the components depicted in FIGS. 1A-1B.

The foregoing description, for purpose of explanation, has beendescribed with reference to specific embodiments. However, theillustrative discussions above are not intended to be exhaustive or tolimit the invention to the precise forms disclosed. Many modificationsand variations are possible in view of the above teachings. Theembodiments were chosen and described in order to best explain theprinciples of the invention and its practical applications, to therebyenable others skilled in the art to best use the invention and variousdescribed embodiments with various modifications as are suited to theparticular use contemplated.

What is claimed is:
 1. A method comprising: at a device including adisplay and one or more input devices: receiving, via the one or moreinput devices, a user input that corresponds with a sequence ofcharacters; and in response to receiving the user input, displaying, onthe display, simulated handwritten text that includes varying theappearance of characters in the simulated handwritten text based onvariations that were detected in handwritten text of a respective user,including: in accordance with a determination that a first criterion ismet, a first character in the sequence of characters has a firstappearance that corresponds to the appearance of the first character inhandwritten text of the respective user; and in accordance with adetermination that a second criterion is met, the first character in thesequence of characters has a second appearance that corresponds to theappearance of the first character in handwritten text of the respectiveuser, wherein the second appearance of the first character is differentthan the first appearance of the first character.
 2. The method of claim1, wherein the first appearance is associated with one or more of afirst line angle, a first line shape and a first line thickness, andwherein the second appearance is associated with one or more of a secondline angle that is different from the first line angle, a second lineshape that is different from the first line shape and a second linethickness that is different from the first line thickness.
 3. The methodof claim 1, wherein the first character includes a first stroke and asecond stroke, wherein the first appearance is associated with a firstproportion between the first stroke and the second stroke, and whereinthe second appearance is associated with a second proportion between thefirst stroke and the second stroke, the second proportion beingdifferent from the first proportion.
 4. The method of claim 1, whereinthe variation between the first appearance and the second appearance isa function of a variation in the handwritten text of the respectiveuser.
 5. The method of claim 1, wherein the one or more input devicesincludes a microphone, and wherein receiving the user input comprises:detecting the user input via the microphone.
 6. The method of claim 1,wherein receiving the user input comprises: receiving the user input viaone or more of a messaging application and a notes application.
 7. Themethod of claim 1, wherein receiving the user input comprises:retrieving an electronic file.
 8. The method of claim 1, furthercomprising: prior to receiving the user input that corresponds with thesequence of characters: receiving the handwritten text of the respectiveuser.
 9. The method of claim 8, further comprising: during an enrollmentfor displaying the simulated handwritten text: displaying a predefinedtext string; and in response to displaying the predefined text string,receiving the handwritten text, wherein the handwritten text correspondswith the predefined text string.
 10. The method of claim 8, wherein thehandwritten text is received outside an enrollment for displaying thesimulated handwritten text.
 11. The method of claim 10, furthercomprising: in response to a determination that an amount of receivedhandwritten text is greater than a threshold amount, presenting anotification indicating that the device has received a sufficient amountof handwritten text to generate the simulated handwritten text.
 12. Themethod of claim 1, further comprising: determining whether one of thefirst criterion and the second criterion are met based on a randomizingfunction.
 13. The method of claim 1, wherein determining that the firstcriterion is met when the first character is between a second characterand a third character, and wherein determining that the second criterionis met when the first character is adjacent the second character and notadjacent the third character.
 14. The method of claim 1, furthercomprising: after displaying the first character in accordance with oneof the first appearance and the second appearance: receiving a secondcharacter in the sequence of characters; and in response to receivingthe second character in the sequence of characters: in accordance with adetermination that a third criterion is met, changing the display of thefirst character from one of the first appearance and the secondappearance to a third appearance that corresponds to the appearance ofthe first character in handwritten text of the respective user; and inaccordance with a determination that a fourth criterion is met, changingthe display of the first character from one of the first appearance andthe second appearance to a fourth appearance that corresponds to theappearance of the first character in handwritten text of the respectiveuser, wherein the fourth appearance of the first character is differentthan the third appearance of the first character.
 15. The method ofclaim 1, further comprising: detecting an input corresponding to arequest to insert a cursor; and in response to detecting the input thatcorresponds to the request to insert the cursor: in accordance with adetermination that the cursor is inserted within the simulatedhandwritten text, displaying a keyboard including characters thatcorrespond with handwritten text of the respective user; and inaccordance with a determination that the cursor is not inserted withinthe simulated handwritten text, displaying the keyboard includingcharacters that correspond with a predetermined font.
 16. The method ofclaim 1, further comprising: synthesizing a font based on thehandwritten text of the respective user; and sharing the font withanother user, wherein the other user can user the font to display textwith one of the first appearance and the second appearance.
 17. Themethod of claim 1, wherein displaying the simulated handwritten textcomprises: displaying the simulated handwritten text as suggested text.18. The method of claim 1, wherein displaying the simulated handwrittentext comprises: in accordance with a determination that a secondcharacter in the sequence of characters does not correspond withhandwritten text of the respective user, synthesizing the secondcharacter based on sub-character features of other characters thatcorrespond with handwritten text of the respective user.
 19. The methodof claim 1, further comprising: detecting an input corresponding to arequest to insert a cursor; receiving, via the one or more inputdevices, a second user input that corresponds with a second sequence ofcharacters; and in response to receiving the second user input: inaccordance with a determination that the cursor is inserted within thesimulated handwritten text, displaying the second sequence of charactersin simulated handwritten text that corresponds with handwritten text ofthe respective user; and in accordance with a determination that thecursor is not inserted within the simulated handwritten text, displayingthe second sequence of characters in a predetermined font.
 20. Themethod of claim 19, further comprising: after detecting the inputcorresponding to the request to insert the cursor: determining whetheror not the cursor is inserted within the simulated handwritten text. 21.An electronic device comprising: a display; one or more input devices;one or processors; and a non-transitory memory storing one or moreprograms, the one or more programs including instructions which, whenexecuted by the one or more processors, cause the electronic device to:receive, via the one or more input devices, a user input thatcorresponds with a sequence of characters; and in response to receivingthe user input, display, on the display, simulated handwritten text thatincludes varying the appearance of characters in the simulatedhandwritten text based on variations that were detected in handwrittentext of a respective user, including: in accordance with a determinationthat a first criterion is met, a first character in the sequence ofcharacters has a first appearance that corresponds to the appearance ofthe first character in handwritten text of the respective user; and inaccordance with a determination that a second criterion is met, thefirst character in the sequence of characters has a second appearancethat corresponds to the appearance of the first character in handwrittentext of the respective user, wherein the second appearance of the firstcharacter is different than the first appearance of the first character.22. The electronic device of claim 21, wherein the first appearance isassociated with one or more of a first line angle, a first line shapeand a first line thickness, and wherein the second appearance isassociated with one or more of a second line angle that is differentfrom the first line angle, a second line shape that is different fromthe first line shape and a second line thickness that is different fromthe first line thickness.
 23. The electronic device of claim 21, whereinthe first character includes a first stroke and a second stroke, whereinthe first appearance is associated with a first proportion between thefirst stroke and the second stroke, and wherein the second appearance isassociated with a second proportion between the first stroke and thesecond stroke, the second proportion being different from the firstproportion.
 24. The electronic device of claim 21, wherein the variationbetween the first appearance and the second appearance is a function ofa variation in the handwritten text of the respective user.
 25. Theelectronic device of claim 21, wherein the one or more input devicesincludes a microphone, and wherein receiving the user input comprises:detecting the user input via the microphone.
 26. The electronic deviceof claim 21, wherein receiving the user input comprises: receiving theuser input via one or more of a messaging application and a notesapplication.
 27. The electronic device of claim 21, wherein receivingthe user input comprises: retrieving an electronic file.
 28. Theelectronic device of claim 21, wherein the instructions further causethe electronic device to: prior to receiving the user input thatcorresponds with the sequence of characters: receive the handwrittentext of the respective user.
 29. The electronic device of claim 28,wherein the instructions further cause the electronic device to: duringan enrollment for displaying the simulated handwritten text: display apredefined text string; and in response to displaying the predefinedtext string, receive the handwritten text, wherein the handwritten textcorresponds with the predefined text string.
 30. The electronic deviceof claim 28, wherein the handwritten text is received outside anenrollment for displaying the simulated handwritten text.
 31. Theelectronic device of claim 30, wherein the instructions further causethe electronic device to: in response to a determination that an amountof received handwritten text is greater than a threshold amount, presenta notification indicating that the device has received a sufficientamount of handwritten text to generate the simulated handwritten text.32. The electronic device of claim 21, wherein the instructions furthercause the electronic device to: determine whether one of the firstcriterion and the second criterion are met based on a randomizingfunction.
 33. The electronic device of claim 21, wherein determiningthat the first criterion is met when the first character is between asecond character and a third character, and wherein determining that thesecond criterion is met when the first character is adjacent the secondcharacter and not adjacent the third character.
 34. The electronicdevice of claim 21, wherein the instructions further cause theelectronic device to: after displaying the first character in accordancewith one of the first appearance and the second appearance: receive asecond character in the sequence of characters; and in response toreceiving the second character in the sequence of characters: inaccordance with a determination that a third criterion is met, changethe display of the first character from one of the first appearance andthe second appearance to a third appearance that corresponds to theappearance of the first character in handwritten text of the respectiveuser; and in accordance with a determination that a fourth criterion ismet, change the display of the first character from one of the firstappearance and the second appearance to a fourth appearance thatcorresponds to the appearance of the first character in handwritten textof the respective user, wherein the fourth appearance of the firstcharacter is different than the third appearance of the first character.35. The electronic device of claim 21, wherein the instructions furthercause the electronic device to: detect an input corresponding to arequest to insert a cursor; and in response to detecting the input thatcorresponds to the request to insert the cursor: in accordance with adetermination that the cursor is inserted within the simulatedhandwritten text, display a keyboard including characters thatcorrespond with handwritten text of the respective user; and inaccordance with a determination that the cursor is not inserted withinthe simulated handwritten text, display the keyboard includingcharacters that correspond with a predetermined font.
 36. The electronicdevice of claim 21, wherein the instructions further cause theelectronic device to: synthesize a font based on the handwritten text ofthe respective user; and share the font with another user, wherein theother user can user the font to display text with one of the firstappearance and the second appearance.
 37. The electronic device of claim21, wherein displaying the simulated handwritten text comprises:displaying the simulated handwritten text as suggested text.
 38. Theelectronic device of claim 21, wherein displaying the simulatedhandwritten text comprises: in accordance with a determination that asecond character in the sequence of characters does not correspond withhandwritten text of the respective user, synthesizing the secondcharacter based on sub-character features of other characters thatcorrespond with handwritten text of the respective user.
 39. Theelectronic device of claim 21, wherein the instructions further causethe electronic device to: detect an input corresponding to a request toinsert a cursor; receive, via the one or more input devices, a seconduser input that corresponds with a second sequence of characters; and inresponse to receiving the second user input: in accordance with adetermination that the cursor is inserted within the simulatedhandwritten text, display the second sequence of characters in simulatedhandwritten text that corresponds with handwritten text of therespective user; and in accordance with a determination that the cursoris not inserted within the simulated handwritten text, display thesecond sequence of characters in a predetermined font.
 40. Theelectronic device of claim 39, wherein the instructions further causethe electronic device to: after detecting the input corresponding to therequest to insert the cursor: determine whether or not the cursor isinserted within the simulated handwritten text.
 41. A non-transitorycomputer readable storage medium storing one or more programs, the oneor more programs comprising instructions, which, when executed by anelectronic device with a display, one or more input devices, cause theelectronic device to: receive, via the one or more input devices, a userinput that corresponds with a sequence of characters; and in response toreceiving the user input, display, on the display, simulated handwrittentext that includes varying the appearance of characters in the simulatedhandwritten text based on variations that were detected in handwrittentext of a respective user, including: in accordance with a determinationthat a first criterion is met, a first character in the sequence ofcharacters has a first appearance that corresponds to the appearance ofthe first character in handwritten text of the respective user; and inaccordance with a determination that a second criterion is met, thefirst character in the sequence of characters has a second appearancethat corresponds to the appearance of the first character in handwrittentext of the respective user, wherein the second appearance of the firstcharacter is different than the first appearance of the first character.42. The non-transitory computer readable storage medium of claim 41,wherein the first appearance is associated with one or more of a firstline angle, a first line shape and a first line thickness, and whereinthe second appearance is associated with one or more of a second lineangle that is different from the first line angle, a second line shapethat is different from the first line shape and a second line thicknessthat is different from the first line thickness.
 43. The non-transitorycomputer readable storage medium of claim 41, wherein the firstcharacter includes a first stroke and a second stroke, wherein the firstappearance is associated with a first proportion between the firststroke and the second stroke, and wherein the second appearance isassociated with a second proportion between the first stroke and thesecond stroke, the second proportion being different from the firstproportion.
 44. The non-transitory computer readable storage medium ofclaim 41, wherein the variation between the first appearance and thesecond appearance is a function of a variation in the handwritten textof the respective user.
 45. The non-transitory computer readable storagemedium of claim 41, wherein the one or more input devices includes amicrophone, and wherein receiving the user input comprises: detectingthe user input via the microphone.
 46. The non-transitory computerreadable storage medium of claim 41, wherein receiving the user inputcomprises: receiving the user input via one or more of a messagingapplication and a notes application.
 47. The non-transitory computerreadable storage medium of claim 41, wherein receiving the user inputcomprises: retrieving an electronic file.
 48. The non-transitorycomputer readable storage medium of claim 41, wherein the instructionsfurther cause the electronic device to: prior to receiving the userinput that corresponds with the sequence of characters: receive thehandwritten text of the respective user.
 49. The non-transitory computerreadable storage medium of claim 48, wherein the instructions furthercause the electronic device to: during an enrollment for displaying thesimulated handwritten text: display a predefined text string; and inresponse to displaying the predefined text string, receive thehandwritten text, wherein the handwritten text corresponds with thepredefined text string.
 50. The non-transitory computer readable storagemedium of claim 48, wherein the handwritten text is received outside anenrollment for displaying the simulated handwritten text.
 51. Thenon-transitory computer readable storage medium of claim 41, wherein theinstructions further cause the electronic device to: in response to adetermination that an amount of received handwritten text is greaterthan a threshold amount, present a notification indicating that thedevice has received a sufficient amount of handwritten text to generatethe simulated handwritten text.
 52. The non-transitory computer readablestorage medium of claim 41, wherein the instructions further cause theelectronic device to: determine whether one of the first criterion andthe second criterion are met based on a randomizing function.
 53. Thenon-transitory computer readable storage medium of claim 41, whereindetermining that the first criterion is met when the first character isbetween a second character and a third character, and whereindetermining that the second criterion is met when the first character isadjacent the second character and not adjacent the third character. 54.The non-transitory computer readable storage medium of claim 41, whereinthe instructions further cause the electronic device to: afterdisplaying the first character in accordance with one of the firstappearance and the second appearance: receive a second character in thesequence of characters; and in response to receiving the secondcharacter in the sequence of characters: in accordance with adetermination that a third criterion is met, change the display of thefirst character from one of the first appearance and the secondappearance to a third appearance that corresponds to the appearance ofthe first character in handwritten text of the respective user; and inaccordance with a determination that a fourth criterion is met, changethe display of the first character from one of the first appearance andthe second appearance to a fourth appearance that corresponds to theappearance of the first character in handwritten text of the respectiveuser, wherein the fourth appearance of the first character is differentthan the third appearance of the first character.
 55. The non-transitorycomputer readable storage medium of claim 41, wherein the instructionsfurther cause the electronic device to: detect an input corresponding toa request to insert a cursor; and in response to detecting the inputthat corresponds to the request to insert the cursor: in accordance witha determination that the cursor is inserted within the simulatedhandwritten text, display a keyboard including characters thatcorrespond with handwritten text of the respective user; and inaccordance with a determination that the cursor is not inserted withinthe simulated handwritten text, display the keyboard includingcharacters that correspond with a predetermined font.
 56. Thenon-transitory computer readable storage medium of claim 41, wherein theinstructions further cause the electronic device to: synthesize a fontbased on the handwritten text of the respective user; and share the fontwith another user, wherein the other user can user the font to displaytext with one of the first appearance and the second appearance.
 57. Thenon-transitory computer readable storage medium of claim 41, whereindisplaying the simulated handwritten text comprises: displaying thesimulated handwritten text as suggested text.
 58. The non-transitorycomputer readable storage medium of claim 41, wherein displaying thesimulated handwritten text comprises: in accordance with a determinationthat a second character in the sequence of characters does notcorrespond with handwritten text of the respective user, synthesizingthe second character based on sub-character features of other charactersthat correspond with handwritten text of the respective user.
 59. Thenon-transitory computer readable storage medium of claim 41, wherein theinstructions further cause the electronic device to: detect an inputcorresponding to a request to insert a cursor; receive, via the one ormore input devices, a second user input that corresponds with a secondsequence of characters; and in response to receiving the second userinput: in accordance with a determination that the cursor is insertedwithin the simulated handwritten text, display the second sequence ofcharacters in simulated handwritten text that corresponds withhandwritten text of the respective user; and in accordance with adetermination that the cursor is not inserted within the simulatedhandwritten text, display the second sequence of characters in apredetermined font.
 60. The non-transitory computer readable storagemedium of claim 59, wherein the instructions further cause theelectronic device to: after detecting the input corresponding to therequest to insert the cursor: determine whether or not the cursor isinserted within the simulated handwritten text.